credcycle
Registry code: 36156fabf2724bbf
Provider credentialing & payer-enrollment tracking for medical practices — read-only demo tools.
from a public catalogue that lists it, not from the operator
- endpoint
- https://credcycle.artificl.us/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- bearer
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is credcycle live?
- Yes — it answered the hub's last check (checked 55m ago). It answered 99% of checks over the last 30 days.
- Is credcycle free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does credcycle have?
- 5 tools: get_credentials_due, export_credentialing_report, search_credentials, list_billing_at_risk, get_credentialing_summary.
- Is credcycle 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.4%· all time 99.4%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- list provider credentials due for renewal
- find providers with billing at risk
- export credentialing report
- takes → gives
- text → data, text
- tools
- 5 reads
- note
- demo or test
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_billing_at_risk reads open 5d ago
List providers with a lapsed or missing credential or payer enrollment — the ones whose claims are denying or about to. Most urgent first.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesget_credentialing_summary reads open 5d ago
Get the credentialing summary: totals for tracked credentials, action needed, lapsed with billing at risk, due in 30 days, and sitting with the payer.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesget_credentials_due reads unknown never probed
List credentials and payer cycles due within the next N days (default 90), including CAQH attestations and re-credentialing packets.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "days": { "type": "number", "description": "Look-ahead window in days (default 90)." } } }arguments 10 linesexport_credentialing_report reads unknown never probed
Export the full credentialing report as CSV text (provider, credential, due date, status, follow-up history).
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linessearch_credentials reads unknown never probed
Search provider credentials by provider name, payer, or credential type. Returns matching records with due date and status (current, with payer, action needed, lapsed).
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "query": { "type": "string", "description": "Text to match against provider or credential (case-insensitive; shorthand like \"recred\" or \"license\" works). Omit to list everything." } } }arguments 10 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 id36156fabf2724bbf.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/36156fabf2724bbf/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/36156fabf2724bbf?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.
- deawatch.artificl.us deawatch
- driverfile.artificl.us driverfile
- hooddue.artificl.us hooddue
- liftlog.artificl.us liftlog
- vendorping.artificl.us vendorping
- subproof.artificl.us subproof.artificl.us