com.borisinc/aegis
REMOTE · AEGIS-MCP.BORISINC.COM · SCANNED SEP 20
Trust layer for the x402 economy - check any service before you pay. Scores, discovery, routing.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the com.borisinc/aegis MCP server?
com.borisinc/aegis is a hosted endpoint at https://aegis-mcp.borisinc.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · aegis-mcp.borisinc.com
claude mcp add --transport http com-borisinc-aegis 'https://aegis-mcp.borisinc.com/mcp'
{
"mcpServers": {
"com-borisinc-aegis": {
"url": "https://aegis-mcp.borisinc.com/mcp"
}
}
} {
"servers": {
"com-borisinc-aegis": {
"type": "http",
"url": "https://aegis-mcp.borisinc.com/mcp"
}
}
} [mcp_servers.com-borisinc-aegis] url = "https://aegis-mcp.borisinc.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-borisinc-aegis": {
"type": "remote",
"url": "https://aegis-mcp.borisinc.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-borisinc-aegis --url 'https://aegis-mcp.borisinc.com/mcp' --transport streamable-http
mcp_servers:
com-borisinc-aegis:
url: "https://aegis-mcp.borisinc.com/mcp" {
"McpServers": {
"com-borisinc-aegis": {
"Transport": "http",
"Url": "https://aegis-mcp.borisinc.com/mcp"
}
}
} assistant mcp add com-borisinc-aegis -t streamable-http -u 'https://aegis-mcp.borisinc.com/mcp'
{
"mcpServers": {
"com-borisinc-aegis": {
"type": "http",
"url": "https://aegis-mcp.borisinc.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 14 Sept 26 +49
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 13 Sept 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 12 Sept 26 0
- Schema quality: 453 → 536 ▼ functional
- New tool “check_before_pay” functional
- 10 Sept 26 0
- Tool “trust_check” rewrote its description, which is the text the model reads security
- 4 Sept 26 0
- Tool “trust_check” rewrote its description, which is the text the model reads security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://aegis-mcp.borisinc.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=borisinc.com | CN=WE1,O=Google Trust Services,C=US | 31 Aug 2026 | 29 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 429cde9ddaf0bf790ef64ba94a7b6b45 |
| SANs: borisinc.com, *.borisinc.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aegis-mcp.borisinc.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| borisinc.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 530 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aegis-mcp.borisinc.com/mcp | HTTP error | 530 | |
| http (plaintext) | http://aegis-mcp.borisinc.com/mcp | HTTPS enforced | 301 | https://aegis-mcp.borisinc.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_before_pay ~83
FREE 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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
discover ~50
Search the Aegis registry of agent-payable services, ranked by verification-backed trust. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| min_trust | number | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
erc8004_reputation ~70
On-chain ERC-8004 reputation for any registered agent (Base IdentityRegistry) + Aegis probe cross-check + divergence flag. Paid $0.005 via x402 (_meta['x402/payment']).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | – | – |
| domain | string | – | – |
No output schema declared.
No examples provided.
procure ~78
TASK+BUDGET procurement: describe what you need in plain language + max spend; Aegis picks the best verified service, executes with failover, captures only on delivery, returns data + Ed25519-signed receipt. Never over budget. Dynamic x402 via _meta.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | yes | – |
| need | string | yes | – |
No output schema declared.
No examples provided.
route ~74
Pay 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.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
route_batch ~58
Pay ONCE, Aegis fulfills MANY verified services with per-item failover. items=[{url|capability, params?}]. Charged only if all deliver. Dynamic x402 via _meta.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
smart_discover ~49
Describe what you need in plain language; Aegis maps it to the best verified services (LLM intent matching). Paid $0.01 via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
trust_check ~74
Paid-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']).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
What is the com.borisinc/aegis MCP server?
com.borisinc/aegis is an MCP server listed in the public MCP registry as com.borisinc/aegis. Trust layer for the x402 economy - check any service before you pay. Scores, discovery, routing. This page covers its hosted endpoint (https://aegis-mcp.borisinc.com/mcp).
Is the com.borisinc/aegis MCP server safe to use?
com.borisinc/aegis scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.borisinc/aegis MCP server expose?
com.borisinc/aegis exposes 8 tools: discover, check_before_pay, smart_discover, trust_check, erc8004_reputation, and 3 more. Their descriptions and schemas cost roughly 536 tokens of context every time the server is loaded.
Does the com.borisinc/aegis MCP server require authentication?
No. We connected to com.borisinc/aegis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.borisinc/aegis MCP server still maintained?
com.borisinc/aegis is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.