digital-compass-mcp
Registry code: e6b8e69bf031688c
Romanian digital-crisis playbooks as tools: match, guide, report. Public good, RO+EN, CC BY 4.0.
from a public catalogue that lists it, not from the operator
- endpoint
- https://compass.madeinro.eu/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 digital-compass-mcp live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is digital-compass-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does digital-compass-mcp have?
- 5 tools: compass_find_playbook, compass_get_content, compass_freshness, compass_list_situations, compass_report_channels.
- Is digital-compass-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
- topic
- security & compliance
- used for
- find playbook for a digital scam or hacked account
- read crisis steps to take
- get reporting channels for digital incidents
- 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.
compass_freshness reads open 15h ago
The date of the last editorial review ("last verified") for every playbook and guide — transparency about how fresh the advice is.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linescompass_list_situations reads open 15h ago
All digital-crisis situations (reactive playbooks: fake link, hacked account, online scam...) and prevention guides covered by Digital Compass, with slugs for compass_get_content. Public Romanian guide, plain language, content in 9 languages. Optional filters: categorie (use case) and audienta (individ/organizatie).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "lang": { "enum": [ "ro", "en", "hu", "pl", "cs", "sk", "it", "fr", "de" ], "type": "string", "default": "ro", "description": "Content language (ro = original; en/hu anchored in Romania; pl/cs/sk/it/fr/de anchored in their own countries, with local reporting channels)" }, "audienta": { "enum": [ "individ", "organizatie" ], "type": "string", "description": "Optional audience filter: individ (private person) or organizatie (company/team). Content marked \"ambele\" matches both." }, "categorie": { "enum": [ "cumparaturi-bani", "conturi-dispozitive", "mesaje-apeluri", "oameni-manipulare", "ai-asistenti", "conturi-parole", "cumparaturi-plati", "dispozitive", "email-mesaje", "la-birou" ], "type": "string", "description": "Optional use-case category filter. Playbook categories: cumparaturi-bani, conturi-dispozitive, mesaje-apeluri, oameni-manipulare, ai-asistenti. Guide categories: conturi-parole, cumparaturi-plati, dispozitive, email-mesaje, la-birou." } }, "additionalProperties": false }arguments 47 linescompass_report_channels reads open 15h ago
Real reporting channels for digital incidents, from the playbooks' "Where to report" sections. lang=ro/en/hu → channels in ROMANIA (DNSC 1911, Romanian Police, your bank); lang=pl → channels in POLAND (CERT Polska, policja, card blocking). With slug: only that situation's channels; without: all, deduplicated.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "lang": { "enum": [ "ro", "en", "hu", "pl", "cs", "sk", "it", "fr", "de" ], "type": "string", "default": "ro", "description": "Content language (ro = original; en/hu anchored in Romania; pl/cs/sk/it/fr/de anchored in their own countries, with local reporting channels)" }, "slug": { "type": "string", "description": "Optional: the slug of one specific playbook" } }, "additionalProperties": false }arguments 27 linescompass_find_playbook reads unknown never probed
Matches the situation in the user's own words ("I clicked a link and it asked for my card") against the covered situations. Deterministic keyword matching (title, situation, summary), not guessing. Returns the best 3 matches with a score.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "query" ], "properties": { "lang": { "enum": [ "ro", "en", "hu", "pl", "cs", "sk", "it", "fr", "de" ], "type": "string", "default": "ro", "description": "Content language (ro = original; en/hu anchored in Romania; pl/cs/sk/it/fr/de anchored in their own countries, with local reporting channels)" }, "query": { "type": "string", "minLength": 3, "description": "The situation, in the user's own words" }, "audienta": { "enum": [ "individ", "organizatie" ], "type": "string", "description": "Optional audience filter: individ (private person) or organizatie (company/team). Content marked \"ambele\" matches both." }, "categorie": { "enum": [ "cumparaturi-bani", "conturi-dispozitive", "mesaje-apeluri", "oameni-manipulare", "ai-asistenti", "conturi-parole", "cumparaturi-plati", "dispozitive", "email-mesaje", "la-birou" ], "type": "string", "description": "Optional use-case category filter. Playbook categories: cumparaturi-bani, conturi-dispozitive, mesaje-apeluri, oameni-manipulare, ai-asistenti. Guide categories: conturi-parole, cumparaturi-plati, dispozitive, email-mesaje, la-birou." } }, "additionalProperties": false }arguments 55 linescompass_get_content reads unknown 8h ago
The full markdown of a crisis playbook (steps to take now, what NOT to do, how to recognize it next time, where to report) or of a prevention guide. Suitable to relay to the user step by step, in document order. In MCP Apps-capable hosts this renders as a calm step-by-step checklist card (ui://compass/playbook-card).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "type", "slug" ], "properties": { "lang": { "enum": [ "ro", "en", "hu", "pl", "cs", "sk", "it", "fr", "de" ], "type": "string", "default": "ro", "description": "Content language (ro = original; en/hu anchored in Romania; pl/cs/sk/it/fr/de anchored in their own countries, with local reporting channels)" }, "slug": { "type": "string", "description": "Slug from compass_list_situations, e.g. \"link-sms-fals\"" }, "type": { "enum": [ "playbook", "ghid" ], "type": "string", "description": "playbook = crisis (reactive), ghid = prevention guide" } }, "additionalProperties": false }arguments 39 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 ide6b8e69bf031688c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/e6b8e69bf031688c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/e6b8e69bf031688c?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.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- tv.madeinro.eu rotv-mcp
- cand-reciclam.madeinro.eu cand-reciclam-mcp