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

copytargets

https://copytargets-al6bxcngia-ue.a.run.app

Registry code: fbe451f785eb17d6

api record
endpoint
https://copytargets-al6bxcngia-ue.a.run.app/mcp
protocol
streamable-http ·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 copytargets live?
Yes — it answered the hub's last check (checked 16h ago). It answered 100% of checks over the last 30 days.
Is copytargets free to use?
Yes — the hub reached it with no key and no payment.
What tools does copytargets have?
2 tools: copy_targets_lite, copy_targets.
Is copytargets 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 100%· all time 100%

latency
162ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 2 tools
2 open 2 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.

  • copy_targets_lite open 16h ago

    FREE lite copy targets. The top 3 ranked tracked Solana wallets with rank, wallet and call only: no scores, no reasons, no sample detail. The paid copy_targets returns the full ranked list with scores, one-line reasons, headline numbers and the sample size behind every wallet.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Optional number of ranked wallets to return (default 10, max 15)."
        }
      }
    }
    arguments 10 lines
  • copy_targets open 16h ago

    Which Solana wallets are worth copying right now, answered as a ranked screening list. Input is optional: a limit (default 10, max 15). Output is the Cluster tracked Solana wallet set scored live with the Copy Check engine, ranked by a 0 to 100 score, each wallet with a COPY / WATCH / SKIP call, a one-line reason, headline numbers (closed trades, realized PnL in SOL from closed trades only, win rate, PnL without the best token, median and p10 hold seconds, trades in the last 7 days, still active flag), and the sample size behind it (closed trades, signatures scanned, swaps parsed). Fail-closed: wallets with fewer than 10 closed trades rank down, map to SKIP, and can never be COPY; COPY requires 20 or more closed trades, positive realized PnL, a 45 to 80 percent win rate, a p10 hold of at least 60 seconds, and a trade in the last 7 days. Every response states the tracked set size and generation stamp, the data basis, and an as-of timestamp. This is a screening tool that ranks by stated criteria; it does not promise profit. Cost: $0.02 USDC per call via x402 (Base settlement; Solana settlement when configured) - no API key needed.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Optional number of ranked wallets to return (default 10, max 15)."
        }
      }
    }
    arguments 10 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 fbe451f785eb17d6.

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