_ registry / mcp http-sse · checked 19m ago

mcpfinder

https://mcpfinder.dsh.sh

Registry code: 678e7ed14ed40cda

api record

Find an MCP server for any task: searches the official registry, Smithery and npm; remote-first. Use when: The user or agent needs a capability (an API, a data source, a SaaS action) and wants to know whether an MCP server already exists for it, which one is maintained and remote, and how to install it. Not for: Calling the found server's tools (install it instead), or building a new MCP server. Every tool takes task_context: one sentence on what the user is trying to do.

endpoint
https://mcpfinder.dsh.sh/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is mcpfinder live?
Yes — it answered the hub's last check (checked 19m ago). It answered 100% of checks over the last 30 days.
Is mcpfinder free to use?
Yes — the hub reached it with no key and no payment.
What tools does mcpfinder have?
2 tools: find_mcp, mcp_details.
Is mcpfinder safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.4%

latency
612ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 329 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • find an mcp server for a task
  • get install details for an mcp server
takes → gives
text → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • find_mcp reads unknown 7h ago

    Search for existing MCP servers that provide a capability (e.g. "postgres", "wayback machine", "google sheets"). Federates the official MCP Registry, Smithery (with live use counts) and npm; dedupes; ranks remote Streamable HTTP servers first. Returns name, description, remote URL or package, popularity, last update and an install snippet. Use before building or asking the user to build a tool.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query",
        "task_context"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 8,
          "maximum": 25,
          "minimum": 1,
          "description": "Max results after ranking. Default 8."
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "What capability you need, as 1-5 keywords (an API name, a product, a data source). Not a sentence."
        },
        "remote_only": {
          "type": "boolean",
          "default": false,
          "description": "Only servers reachable over HTTP without installing anything locally."
        },
        "task_context": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need."
        }
      }
    }
    arguments 34 lines
  • mcp_details reads unknown 7h ago

    Get one MCP server's tool list, transports and install details by its name as returned by find_mcp (registry name like "io.github.owner/server", "smithery:owner/server", or "npm:package"). Use to check a server exposes the tool you need before installing it.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "name",
        "task_context"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 200,
          "minLength": 3,
          "description": "Exact name from find_mcp results."
        },
        "task_context": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need."
        }
      }
    }
    arguments 22 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 678e7ed14ed40cda.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/678e7ed14ed40cda/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/678e7ed14ed40cda/badge.svg)](https://brick.blue/agent/678e7ed14ed40cda?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on dsh.sh 4 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.