_ registry / mcp + a2a JSONRPC · checked 2h ago

Sombra

listed under this name in a public catalogue; the server gives only its address, sombra.so

https://sombra.so

Registry code: baa70fbaf93d90c3

api record

AI research library. Save, organise and reuse notes and webpages as clean markdown context.

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

endpoint
https://sombra.so/mcp
door code
2e9094e7cfe11192
protocol
JSONRPC ·0.2
authentication
bearer
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 Sombra live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is Sombra 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 Sombra have?
21 tools: list_workspaces, browse_collections, read_collection, list_inbox, save_url, fetch_artifact, update_artifact, create_artifact, ….
Is Sombra 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.6%

90 days 99.4%· all time 99.4%

latency
151ms

last good check

priced tools
0

of 21 tools

_ answered our checks, 90 days 963 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • save notes and webpages as markdown
  • reuse research context
takes → gives
text, web pages → text
_ 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 21 tools
21 auth-required 21 of 21 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.

  • list_workspaces auth-required never probed

    List all workspaces you have access to, showing which one is currently active

    workspacesmeta

  • browse_collections auth-required never probed

    Browse your Sombra collections returning title, id and description

    collectionsbrowse

  • read_collection auth-required never probed

    Read the full content from a specific Sombra collection

    collectionsread

  • list_inbox auth-required never probed

    List recent unsorted artifacts not in any collection

    artifactsbrowse

  • save_url auth-required never probed

    Save a web page to your collection by URL

    saveweb

  • fetch_artifact auth-required never probed

    Fetch a single artifact by ID

    artifactsread

  • update_artifact auth-required never probed

    Update an artifact's metadata or content

    artifactsupdate

  • create_artifact auth-required never probed

    Create a new note artifact with markdown content

    artifactscreate

  • delete_artifact auth-required never probed

    Delete an artifact (archives it, content is preserved)

    artifactsdelete

  • list_archived auth-required never probed

    List all archived (deleted) artifacts

    artifactsarchive

  • restore_artifact auth-required never probed

    Restore a previously deleted artifact

    artifactsrestore

  • search_artifacts auth-required never probed

    Search through all saved artifacts by title, content, or URL

    search

  • move_artifact auth-required never probed

    Move a single artifact to a different collection

    artifactsorganize

  • bulk_move_artifacts auth-required never probed

    Move multiple artifacts to a different collection in one operation

    artifactsorganize

  • remove_from_collection auth-required never probed

    Remove an artifact from a collection (moves it back to unsorted)

    collectionsorganize

  • create_collection auth-required never probed

    Create a new collection to organize saved content

    collectionscreate

  • update_collection auth-required never probed

    Update an existing collection's metadata

    collectionsupdate

  • delete_collection auth-required never probed

    Delete a collection (archives it, artifacts are preserved)

    collectionsdelete

  • write_collection_context auth-required never probed

    Write distilled context/summary to a collection

    collectionscontext

  • verify_collection_context auth-required never probed

    Mechanically verify the substantive claims in a distilled context against the collection's source artifacts; returns per-sentence verdicts (anchored / loose / uncited)

    collectionscontextverify

  • read_collection_context auth-required never probed

    Read the distilled context/summary from a collection

    collectionscontext

_ try it over a2a 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 baa70fbaf93d90c3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/baa70fbaf93d90c3/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/baa70fbaf93d90c3/badge.svg)](https://brick.blue/agent/baa70fbaf93d90c3?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 knowoff the mcp door
card completeness
20%

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.