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

sociallinks

https://sociallinks.dev

Registry code: 5979cc5590721d0f

api record

sociallinks.dev finds a creator's accounts on other platforms from one profile URL (Instagram, TikTok, YouTube or X). Use lookup_creator for one creator; it answers live in 10–40 seconds (instantly when the creator is already known). Use start_batch and get_batch for up to 500 at once. Each creator found costs 1 credit; lookups that find nothing are free, and so are repeats your account paid for in the last 30 days. check_balance is free. Pass profile pages, not posts, reels, shorts or videos. Every returned account has a verdict, a net confidence score (0–1) and the evidence for the match;…

endpoint
https://sociallinks.dev/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 sociallinks live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is sociallinks free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does sociallinks have?
4 tools: check_balance, get_batch, lookup_creator, start_batch.
Is sociallinks 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
326ms

last good check

priced tools
0

of 4 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 4 tools
4 auth-required 4 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.

  • check_balance auth-required 1h ago

    Credits left on the account behind the API key. Free.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_batch auth-required 1h ago

    Progress and the rows found so far for a batch started with start_batch.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The batch id from start_batch."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • lookup_creator auth-required never probed

    Find a creator's accounts on the other platforms from one Instagram, TikTok, YouTube or X profile URL. Returns the creator, each account with its verdict, net confidence (0–1) and evidence, and any websites. 1 credit when at least one account is found; free otherwise.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "A creator's profile page, e.g. https://www.instagram.com/mkbhd. Not a post, reel, short or video."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • start_batch auth-required never probed

    Queue up to 500 profile URLs to look up in the background. Returns a batch id; poll it with get_batch. Each row is charged only if it finds accounts.

    mcp-tool

    {
      "type": "object",
      "required": [
        "urls"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Optional label for the batch."
        },
        "urls": {
          "type": "array",
          "items": {
            "type": "string",
            "description": "A creator's profile page, e.g. https://www.instagram.com/mkbhd. Not a post, reel, short or video."
          },
          "maxItems": 500,
          "minItems": 1
        }
      },
      "additionalProperties": false
    }
    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 5979cc5590721d0f.

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