agentic-tools
Registry code: 61b026321de4f910
Audits websites for agent readiness and generates or validates agentic.txt and agentic.json profiles against the bundled Agentic specification.
- endpoint
- https://ruagentic.org/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 agentic-tools live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
- Is agentic-tools free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does agentic-tools have?
- 5 tools: audit_agentic_url, discover_agentic_site, generate_agentic_profile, validate_agentic_profile, get_agentic_spec.
- Is agentic-tools 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 98.6%· all time 98.6%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- audit a site's agentic profile
- generate agentic.txt and agentic.json
- validate an agentic profile
- takes → gives
- web pages, data → 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.
get_agentic_spec reads open 14h ago
Read the Agentic specification bundled with this checkout.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {}, "additionalProperties": false }arguments 6 linesaudit_agentic_url reads unknown 11h ago
Audit a website or public HTTPS Agentic JSON URL. Check the profile, API operations, matching agentic.txt, README.md links, and publication readiness with specific remedies. Does not execute actions.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "url" ], "properties": { "url": { "type": "string", "maxLength": 2048 }, "readmeUrl": { "type": "string", "maxLength": 2048 } }, "additionalProperties": false }arguments 18 linesdiscover_agentic_site reads unknown 11h ago
Read a public website, documentation, OpenAPI and advertised MCP links; generate agentic.txt and agentic.json. No action execution or MCP tool invocation.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "url" ], "properties": { "url": { "type": "string", "maxLength": 2048 } }, "additionalProperties": false }arguments 14 linesgenerate_agentic_profile reads unknown 14h ago
Create a ticket-contract profile for a canonical HTTPS origin. Returns data; does not write files or call a service.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "origin" ], "properties": { "origin": { "type": "string", "maxLength": 2048 }, "actionId": { "type": "string", "maxLength": 80 } }, "additionalProperties": false }arguments 18 linesvalidate_agentic_profile reads unknown 14h ago
Validate JSON profile text and optional OpenAPI JSON text locally. No URL fetching or action execution.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "profile" ], "properties": { "openapi": { "type": "string", "maxLength": 262144 }, "profile": { "type": "string", "maxLength": 65536 } }, "additionalProperties": false }arguments 18 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 id61b026321de4f910.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/61b026321de4f910/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/61b026321de4f910?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.