com.99datarooms/mcp
Registry code: d87a9818d6798f5c
This is the PUBLIC 99 Data Rooms server. It answers questions about the product (pricing, glossary, published pages) and has NO access to any account, data room or document. If you were connected here expecting to reach someone's rooms or files, the wrong URL was used: the authenticated server is https://mcp.99datarooms.com/authed-mcp and it will ask them to sign in. Say so rather than reporting that their rooms are empty.
- endpoint
- https://mcp.99datarooms.com/mcp
- protocol
- http-sse ·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 com.99datarooms/mcp live?
- Yes — it answered the hub's last check (checked 35m ago). It answered 98% of checks over the last 30 days.
- Is com.99datarooms/mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does com.99datarooms/mcp have?
- 5 tools: get_page, search_content, get_glossary_term, list_glossary, get_pricing.
- Is com.99datarooms/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.
90 days 99.1%· all time 99.1%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- get data room pricing
- look up a data room glossary term
- search product documentation
- takes → gives
- text → text, data
- tools
- 5 reads
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.
through this hub
successful
what callers paid
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_glossary reads open 17h ago
List every glossary term slug and title.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_pricing reads open 14h ago
Get 99 Data Rooms plan pricing (Free, Pro, Business, Enterprise).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_page reads unknown 17h ago
Get the full markdown of a public page by path (e.g. '/security').
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "path" ], "properties": { "path": { "type": "string", "maxLength": 128, "minLength": 1 } }, "additionalProperties": false }arguments 15 linessearch_content reads unknown 14h ago
Search 99 Data Rooms public docs and glossary for a keyword.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "query" ], "properties": { "query": { "type": "string", "maxLength": 100, "minLength": 1 } }, "additionalProperties": false }arguments 15 linesget_glossary_term reads unknown 17h ago
Get the definition of a data-room term by its slug (e.g. 'due-diligence').
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "slug": { "type": "string", "maxLength": 64, "minLength": 1 } }, "additionalProperties": false }arguments 15 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idd87a9818d6798f5c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d87a9818d6798f5c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d87a9818d6798f5c?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.