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

linkame-mcp

https://linkame-a5883.web.app

Registry code: e4f2946f068f8fc3

api record

Access authorized Linkame contacts, profiles, events, tickets and matching results.

from a public catalogue that lists it, not from the operator

endpoint
https://linkame-a5883.web.app/mcp
protocol
streamable-http ·2025-03-26
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 linkame-mcp live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is linkame-mcp 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 linkame-mcp have?
13 tools: account.get_current_user, contacts.get_timeline, events.list, events.get, events.get_my_ticket, events.get_matching_status, profile.get_me, contacts.get, ….
Is linkame-mcp 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
111ms

last good check

priced tools
0

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

  • account.get_current_user auth-required 4h ago

    Restituisce il profilo base dell’utente autenticato.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • contacts.get_timeline auth-required never probed

    Restituisce la timeline di un contatto della rubrica.

    mcp-tool

    {
  "type": "object",
  "required": [
    "contactId"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    },
    "contactId": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • events.list auth-required never probed

    Elenca gli eventi pubblicati visibili all’utente.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • events.get auth-required never probed

    Restituisce i dettagli di un evento pubblicato o gestito dall’utente.

    mcp-tool

    {
  "type": "object",
  "required": [
    "eventId"
  ],
  "properties": {
    "eventId": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • events.get_my_ticket auth-required never probed

    Restituisce un biglietto dell’utente. Il QR viene incluso solo se richiesto esplicitamente.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticketId"
  ],
  "properties": {
    "ticketId": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
    },
    "includeQrCode": {
      "type": "boolean"
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • events.get_matching_status auth-required never probed

    Restituisce lo stato dell’ultimo matching dell’utente, eventualmente filtrato per evento.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "eventId": {
      "type": "string",
      "maxLength": 200
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • profile.get_me auth-required never probed

    Restituisce i profili Linkame dell’utente autenticato.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • contacts.get auth-required never probed

    Restituisce un contatto della rubrica usando il suo identificatore stabile.

    mcp-tool

    {
  "type": "object",
  "required": [
    "contactId"
  ],
  "properties": {
    "contactId": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • events.list_my_registrations auth-required never probed

    Elenca gli eventi ai quali l’utente risulta registrato.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • events.list_my_tickets auth-required never probed

    Elenca i biglietti posseduti o trasferiti all’utente senza esporre il QR.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • events.get_matching_results auth-required 4h ago

    Restituisce i risultati dell’ultimo matching completato dell’utente.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "eventId": {
      "type": "string",
      "maxLength": 200
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • contacts.list_groups auth-required 4h ago

    Restituisce i gruppi di contatti dell’utente, inclusi gli inviti pendenti.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • contacts.search auth-required never probed

    Cerca nella rubrica dell’utente per nome, azienda, ruolo, email, tag o note.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    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 e4f2946f068f8fc3.

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

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.