agent-signals
https://agent-signals.saromy-export.workers.dev
Registry code: 4d008544ac3c167b
Search sourced French public procurement notices from official BOAMP open data.
from a public catalogue that lists it, not from the operator
- endpoint
- https://agent-signals.saromy-export.workers.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 agent-signals live?
- Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
- Is agent-signals free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does agent-signals have?
- 3 tools: data_sources, ecosystem_catalog, search_public_tenders.
- Is agent-signals 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 100%· all time 100%
last good check
of 3 tools
- unknown → live
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
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
data_sources unknown never probed
Describe the official BOAMP dataset, provenance, reuse conditions and limitations of this experimental public tender search.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesecosystem_catalog unknown never probed
Find related MCP services: Agent Guardian (contract audit), Agent Repair (failed tool calls), and Agent Signals (public-data search). No automatic redirect or payment.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linessearch_public_tenders unknown 13h ago
Search recent French public-procurement notices in the official DILA BOAMP open dataset. Keyword in notice title; returns bounded, sourced records with publication and deadline. Free beta, not exhaustive, no private data or scraped websites.
{ "type": "object", "required": [ "keyword" ], "properties": { "keyword": { "type": "string", "maxLength": 40, "minLength": 2, "description": "Short French tender keyword e.g. granulés, maintenance, travaux. No user-controlled SQL or URLs." }, "days_back": { "type": "integer", "maximum": 60, "minimum": 1, "description": "How far back to search; default 30 days." }, "max_results": { "type": "integer", "maximum": 5, "minimum": 1, "description": "Maximum notices returned; default 5." }, "strict_match": { "type": "boolean", "description": "Default true: after official fuzzy search, require normalized literal keyword in notice subject to reduce false positives." } }, "additionalProperties": false }arguments 31 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 id4d008544ac3c167b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4d008544ac3c167b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4d008544ac3c167b?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.