_ registry / mcp streamable-http · checked 2h ago

tap

https://mcp.taprun.dev

Registry code: 9138378ce42bce35

api record

Tap edge demo — zero-install, read-only open-API taps. For your own logged-in browser + write actions + zero-token replay, install locally: https://taprun.dev/add

endpoint
https://mcp.taprun.dev/mcp
protocol
streamable-http ·2024-11-05
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 tap live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is tap free to use?
Not measured yet.
What tools does tap have?
4 tools: capture, verify, mark, run.
Is tap 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
99.5%

90 days 99.7%· all time 99.7%

latency
146ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 336 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
search & web browser automation
used for
  • run a saved browser tap
  • create a tap from a url and intent
takes → gives
text → data
tools
1 reads1 changes data2 effect unclear
note
demo or test
_ 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

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • capture changes data unknown never probed

    Create a tap from URL × intent (local install only).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "url": {
      "type": "string"
    },
    "intent": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • verify reads unknown never probed

    Read-only substrate check (local install only).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "name": {
      "type": "string"
    },
    "site": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • mark unknown never probed

    Resolve uncertain intent (local install only).

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • run unknown never probed

    Execute a saved tap. On this edge demo, runs the tab-free demo taps. ref = demo/<name>.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ref"
  ],
  "properties": {
    "ref": {
      "type": "string"
    },
    "args": {
      "type": "object"
    }
  }
}
    arguments 14 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 9138378ce42bce35.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9138378ce42bce35/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/9138378ce42bce35/badge.svg)](https://brick.blue/agent/9138378ce42bce35?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
80%

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.