com.secureauth/agent-authority
SecureAuth Agent Authority
Is the SecureAuth Agent Authority MCP server down? No. It is up and needs your URL, probed 2026-10-26.
Identity-first enterprise MCP gateway: per-call authorization, agent identity and audit trail
needs your URL probed 2026-11-15 · unchanged since 2026-10-26
The URL has placeholders that each user fills in: {gateway_host}.- Endpoint
- https://{gateway_host}/gateway/mcp (streamable-http)
- Host
- {gateway_host}
- Website
- https://secureauth.com/capabilities/mcp-authority
- Registry
- active, updated 2026-10-23 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Other registry entries on {gateway_host}.
- TruOptim Industrial AI Gateway com.truoptim/industrial-ai-gateway · needs your URL
Servers that mention authority.
- TrustGrowth ai.trustgrowth/trustgrowth · needs auth
- app.certman/server · needs auth
- JassWiki — Swiss Jass Authority (AMCP v0.1) ch.jassverband/jasswiki · alive
- ALEETH Authority MCP com.aleeth/authority-mcp · needs auth
- AITWIRE com.aitwire/authority · alive
- apix402 com.api402x/apix402 · timeout
- CarrierScrub com.carrierscrub/carrier-lookup · needs auth
- Corpole com.corpole/requirements · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-26 08:58 | needs your URL | ||||
| 2026-10-24 08:25 | no DNS |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- Every URL of the registry entry has a placeholder that each user fills in, such as a tenant, a project or a host of their own. Without that value there is nothing to call, so the probe does not call the URL, and the entry is not counted as down. A client asks the user for the value.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.