thruact
Registry code: 6874f73a2a690920
Name the job, not the vendor. Routes a provider, fails over, catalog off the tool list.
from a public catalogue that lists it, not from the operator
- endpoint
- https://thruact.com/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 thruact live?
- Yes — it answered the hub's last check (checked 32m ago). It answered 100% of checks over the last 30 days.
- Is thruact free to use?
- Not measured yet.
- What tools does thruact have?
- 7 tools: thruact_compare, thruact_wallet, thruact_iq, thruact_call, thruact_discover, thruact_act, thruact_proxy.
- Is thruact 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 7 tools
- degraded → live
- unknown → live
- used for
- run a capability across providers
- find capabilities with prices
- compare provider answers
- proxy a request to a connected vendor
- check prepaid balance
- takes → gives
- text, data → text, data
- tools
- 4 reads3 effect unclear
- note
- resells another provider
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.
thruact_compare reads unknown never probed
Ask every provider behind a capability the same question at once and report where their answers differ. Use it when the answer matters enough to want it corroborated. Costs more than act: every provider called is paid.
{ "type": "object", "required": [ "capability" ], "properties": { "input": { "type": "object" }, "providers": { "type": "integer", "description": "How many providers to ask. Omit for all of them." }, "capability": { "type": "string" } } }arguments 18 linesthruact_wallet reads unknown never probed
Prepaid balance and recent charges.
{ "type": "object", "properties": {} }arguments 4 linesthruact_iq reads unknown never probed
Measured reliability per tool over the last 7 days.
{ "type": "object", "properties": { "capability": { "type": "string" } } }arguments 8 linesthruact_call unknown never probed
Run one specific tool by id. No failover.
{ "type": "object", "required": [ "tool" ], "properties": { "tool": { "type": "string" }, "params": { "type": "object" } } }arguments 14 linesthruact_discover reads unknown never probed
Find capabilities for a job, with prices and measured reliability. Search first, execute second.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "description": "Max candidates" }, "query": { "type": "string", "description": "Natural language job" } } }arguments 16 linesthruact_act unknown never probed
Run a capability. Routes across providers and fails over automatically on provider faults. The reply's `route` says which providers were considered, what each scored, and why any were not used — including ones dropped for a missing credential.
{ "type": "object", "required": [ "capability" ], "properties": { "hedge": { "type": "boolean", "description": "Race a backup provider if the first is slower than usual. Cuts tail latency; you are charged for one answer." }, "input": { "type": "object" }, "prefer": { "enum": [ "cheapest", "fastest" ], "type": "string", "description": "What to optimise for among the providers that fit the ceiling." }, "capability": { "type": "string" }, "max_cost_usd": { "type": "number", "description": "Ceiling for this call. Narrows which providers may be used rather than refusing outright; if nothing fits, the error names the cheapest price that would." } } }arguments 30 linesthruact_proxy unknown never probed
Send an authenticated request to a third-party vendor the workspace has connected. The stored API key is injected server-side — you never see it. Give the vendor id from the directory (e.g. openai, sendgrid), an HTTP method, and a path on that vendor's own API. Use it to act through a connected vendor that is not a Thruact capability. Metered per call.
{ "type": "object", "required": [ "vendor", "path" ], "properties": { "body": { "type": "object", "description": "JSON request body for POST/PUT/PATCH" }, "path": { "type": "string", "description": "Path on the vendor's API, e.g. /v1/models" }, "method": { "enum": [ "GET", "POST", "PUT", "PATCH", "DELETE" ], "type": "string" }, "vendor": { "type": "string", "description": "Vendor id from the directory" } } }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 id6874f73a2a690920.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/6874f73a2a690920/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/6874f73a2a690920?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.