Koskamo

Ethos MCP

An official MCP server provided by Ethos that exposes reputation and credibility lookup tools for AI agents. It allows querying credibility scores, user profiles by X handle or wallet address, user searches, and XP history without requiring authentication or API keys, serving as a read-only interface to Ethos's reputation data.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Ethos MCP logo, by EthosVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Ethos
MCP endpoint (Streamable HTTP)
https://developers.ethos.network/mcp
Vendor documentation

What its tools do

5 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

5 of 5 have a description · 5 of 5 declare behavior hints · 5 of 5 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to ethos.network ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve credibility scores for specific user keys
  • Look up Ethos profiles associated with X handles or wallet addresses
  • Search for users by name, handle, or address fragments
  • Fetch total XP history for a user across all seasons

Source and maintenance

Vendor evidenceRegistry 1.0.0
Maintenance checked

Protocol and capabilities

Server
ethos 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
5 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Ethos is a reputation network for crypto: people review each other, vouch with staked ETH, and link wallets and social accounts to one profile. These tools answer "can I trust this wallet, X account or person?" They are read-only and free. Which tool: ethos_score for a quick trust check (score 0 to 2800; below 800 untrusted, 800 to 1199 questionable, 1200 to 1399 neutral, 1400 and up increasingly reputable, to renowned); ethos_user_by_x or ethos_user_by_address for the full profile behind an X handle or wallet, including every linked account; ethos_search_users when you only have a name or fragment; ethos_xp to weigh how much history backs a score. A userkey is address:0x…, profileId:<n>, service:x.com:username:<handle>, service:x.com:<account id>, service:discord:<id> or service:telegram:<id>. Typical flows: before a trade or transfer, look up the counterparty address; when a user asks about an account, search by name, then score the match; to rank or filter accounts, score each. Scores reflect peer judgement and can be gamed at the margins, so treat them as a strong signal, not a verdict. The full API (250+ operations, including writes with an API key) is documented at https://developers.ethos.network and free with an X-Ethos-Client header at https://api.ethos.network/api/v2.

Tools

5 advertised

ethos_score — Credibility score for a userkey
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Is this wallet, X account or person trustworthy? Ethos credibility score (0 to 2800) and level, from untrusted to renowned, built from peer reviews, ETH-backed vouches, slashes and linked on-chain and social history. Use it before trading with, following, quoting or paying an unknown counterparty, to rank accounts by reputation, or to flag likely scams and bots. Takes an EVM address, X handle or account id, Discord or Telegram id, or Ethos profile id. Free, no payment or key; the same answer as the free Ethos API. Example input: {"userkey":"service:x.com:username:ethos_network"}. Example output: {"score":2441,"level":"revered"}

ethos_score input schema
{
  "type": "object",
  "required": [
    "userkey"
  ],
  "properties": {
    "userkey": {
      "type": "string",
      "description": "An Ethos userkey: address:0x… (EVM address), profileId:<n>, service:x.com:<X account id>, service:x.com:username:<X handle>, service:discord:<id> or service:telegram:<id>."
    }
  }
}
ethos_score annotations
{
  "title": "Credibility score for a userkey",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
ethos_user_by_x — Ethos user by X (Twitter) handle or account id
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Who is behind an X (Twitter) handle, and can they be trusted? The Ethos profile for a handle or numeric account id: display name, credibility score and status, every wallet address and social account linked to the same person, XP, influence factor, and how many positive, neutral and negative reviews and vouches they have received. Use it to vet an account before engaging, resolve a handle to its wallets, or enrich a mention with reputation. Free, no payment or key; the same answer as the free Ethos API. Example input: {"handle":"ethos_network"}. Example output: {"id":32936,"profileId":1,"displayName":"Ethos","username":"ethos_network","avatarUrl":"https://pbs.twimg.com/profile_images/2074951227599646720/85k3GJ-s.jpg","score":2441,"status":"ACTIVE","userkeys":["profileId:1","service:x.com:1234567890","address:0x1234…"],"xpTotal":4076702,"influenceFactor":276,"stats":{"review":{"received":{"positive":120,"neutral":3,"negative":2}},"vouch":{"received":{"count":40}}}}

ethos_user_by_x input schema
{
  "type": "object",
  "required": [
    "handle"
  ],
  "properties": {
    "handle": {
      "type": "string",
      "description": "X handle without the @, or the numeric X account id."
    }
  }
}
ethos_user_by_x annotations
{
  "title": "Ethos user by X (Twitter) handle or account id",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
ethos_user_by_address — Ethos user by EVM address
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Who owns this wallet, and what is their reputation? The Ethos profile holding an EVM address: display name, X handle and other linked accounts, credibility score and status, XP, influence factor, and review and vouch counts. Use it to attach a name and trust level to a counterparty address before a trade, transfer, airdrop or allowlist decision, or to screen addresses in a transaction for known bad actors. Free, no payment or key; the same answer as the free Ethos API. Example input: {"address":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"}. Example output: {"id":32936,"profileId":1,"displayName":"vitalik.eth","username":null,"avatarUrl":"https://pbs.twimg.com/profile_images/2074951227599646720/85k3GJ-s.jpg","score":1311,"status":"INACTIVE","userkeys":["profileId:1","service:x.com:1234567890","address:0x1234…"],"xpTotal":4076702,"influenceFactor":276,"stats":{"review":{"received":{"positive":120,"neutral":3,"negative":2}},"vouch":{"received":{"count":40}}}}

ethos_user_by_address input schema
{
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$",
      "description": "EVM address, 0x-prefixed."
    }
  }
}
ethos_user_by_address annotations
{
  "title": "Ethos user by EVM address",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
ethos_search_users — Search Ethos users
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Find a person or project on Ethos when you only have a name, a partial handle or part of an address. Returns matching profiles with credibility score, status, linked wallets and social accounts, paginated. The starting point when a user asks about someone by name: search, pick the match, then score or profile it by userkey. Also useful for disambiguating impersonators from the real account. Free, no payment or key; the same answer as the free Ethos API. Example input: {"query":"vitalik","limit":"5"}. Example output: {"values":[{"id":32936,"profileId":1,"displayName":"Ethos","username":"ethos_network","avatarUrl":"https://pbs.twimg.com/profile_images/2074951227599646720/85k3GJ-s.jpg","score":2441,"status":"ACTIVE","userkeys":["profileId:1","service:x.com:1234567890","address:0x1234…"],"xpTotal":4076702,"influenceFactor":276,"stats":{"review":{"received":{"positive":120,"neutral":3,"negative":2}},"vouch":{"received":{"count":40}}}}],"total":1,"limit":5,"offset":0}

ethos_search_users input schema
{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Results per page, default 10."
    },
    "query": {
      "type": "string",
      "description": "Name, handle or address fragment to search for."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Results to skip, for paging."
    }
  }
}
ethos_search_users annotations
{
  "title": "Search Ethos users",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
ethos_xp — Total XP for a userkey
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

How active and invested is this person in the Ethos reputation network? Total XP earned across all seasons for a userkey (address, X handle or id, Discord or Telegram id, or profile id). XP accrues from reviews, vouches, invitations and other contributions, so it separates long-standing, engaged members from fresh or dormant accounts. Use it alongside the credibility score to weigh how much history stands behind a reputation. Free, no payment or key; the same answer as the free Ethos API. Example input: {"userkey":"profileId:1"}. Example output: 4076702

ethos_xp input schema
{
  "type": "object",
  "required": [
    "userkey"
  ],
  "properties": {
    "userkey": {
      "type": "string",
      "description": "An Ethos userkey: address:0x… (EVM address), profileId:<n>, service:x.com:<X account id>, service:x.com:username:<X handle>, service:discord:<id> or service:telegram:<id>."
    }
  }
}
ethos_xp annotations
{
  "title": "Total XP for a userkey",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
665 ms
95th percentile latency
665 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 665 ms · metadata changed · 5 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http ethos-mcp https://developers.ethos.network/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add ethos-mcp --url https://developers.ethos.network/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable ethos-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "ethos-mcp": {
      "url": "https://developers.ethos.network/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "ethos-mcp": {
      "type": "streamableHttp",
      "url": "https://developers.ethos.network/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start ethos-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "ethos-mcp": {
      "type": "http",
      "url": "https://developers.ethos.network/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http ethos-mcp https://developers.ethos.network/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://developers.ethos.network/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "ethos-mcp": {
      "serverUrl": "https://developers.ethos.network/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Ethos MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Ethos MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing