com.borisinc/aegis
com.borisinc/aegis · 1.2.0
Trust layer for the x402 economy - check any service before you pay. Scores, discovery, routing.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 35 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://aegis-mcp.borisinc.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 8 tools.
- Protocol
- 2025-06-18
- Calls itself
- aegis 1.28.1
- Handshake time
- 720 ms
- HTTP status
- 200
The tools it lists (8, as of 6 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
discoverSearch the Aegis registry of agent-payable services, ranked by verification-backed trust. Free.
check_before_payFREE preflight BEFORE you pay: should you pay THIS endpoint? Stored verification signals only (no probe, no spend) - registered?, payment-worthiness, confidence, coverage, reasons, evidence. The top of the funnel for the paid trust_check, which adds the fresh probe pass + ERC-8004 on-chain reputation. Free.
smart_discoverDescribe what you need in plain language; Aegis maps it to the best verified services (LLM intent matching). Paid $0.01 via x402.
trust_checkPaid-delivery-verified trust verdict BEFORE you pay: score, tier, recommendation, and explainable confidence+reasons+evidence (Aegis pays real money to confirm delivery; coverage-only scores cannot). Paid $0.05 via x402 (_meta['x402/payment']).
erc8004_reputationOn-chain ERC-8004 reputation for any registered agent (Base IdentityRegistry) + Aegis probe cross-check + divergence flag. Paid $0.005 via x402 (_meta['x402/payment']).
route_batchPay ONCE, Aegis fulfills MANY verified services with per-item failover. items=[{url|capability, params?}]. Charged only if all deliver. Dynamic x402 via _meta.
routePay THROUGH Aegis: we buy the best verified service for you (by url or capability) and relay the data, failing over if one is down. One integration reaches the whole registry; not charged if nothing delivers. Dynamic x402 price via _meta.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.borisinc/aegis, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 81 days ago. The registry entry