mcp-registry/network.tenzro/tenzro/oauth_discovery / alternatives

Live alternatives to mcp-registry/network.tenzro/tenzro/oauth_discovery

The best live alternatives to mcp-registry/network.tenzro/tenzro/oauth_discovery right now are mcp-registry/co.ainumbers/tools/audit_mcp_oauth, mcp-registry/io.github.cthulhutoo/agentry/a2a_public_discovery_api_agents_public_get, mcp-registry/io.github.pipeworx-io/data-oakland/metadata, mcp-registry/cloud.theprotocol/registry/theprotocol_oauthIntrospect, mcp-registry/co.ainumbers/tools/validate_mcp_authorization_metadata — capability-matched and ranked by current reliability. mcp-registry/network.tenzro/tenzro/oauth_discovery itself is currently "healthy".

alternativeserver
mcp-registry/co.ainumbers/tools/audit_mcp_oauthco.ainumbers/toolslive status →
mcp-registry/io.github.cthulhutoo/agentry/a2a_public_discovery_api_agents_public_getio.github.cthulhutoo/agentrylive status →
mcp-registry/io.github.pipeworx-io/data-oakland/metadataio.github.pipeworx-io/data-oaklandlive status →
mcp-registry/cloud.theprotocol/registry/theprotocol_oauthIntrospectcloud.theprotocol/registrylive status →
mcp-registry/co.ainumbers/tools/validate_mcp_authorization_metadataco.ainumbers/toolslive status →
mcp-registry/io.github.pipeworx-io/data-ny/metadataio.github.pipeworx-io/data-nylive status →
mcp-registry/io.github.pipeworx-io/data-cityofchicago/metadataio.github.pipeworx-io/data-cityofchicagolive status →
mcp-registry/io.github.pipeworx-io/data-oregon/metadataio.github.pipeworx-io/data-oregonlive status →
mcp-registry/cloud.theprotocol/registry/theprotocol_getOAuthFederationStatuscloud.theprotocol/registrylive status →
mcp-registry/io.github.pipeworx-io/data-orlando/metadataio.github.pipeworx-io/data-orlandolive status →
mcp-registry/io.github.pipeworx-io/data-pa/metadataio.github.pipeworx-io/data-palive status →
mcp-registry/io.github.pipeworx-io/data-fcc/metadataio.github.pipeworx-io/data-fcclive status →

FAQ

What is the best alternative to mcp-registry/network.tenzro/tenzro/oauth_discovery?

mcp-registry/co.ainumbers/tools/audit_mcp_oauth is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.cthulhutoo/agentry/a2a_public_discovery_api_agents_public_get, mcp-registry/io.github.pipeworx-io/data-oakland/metadata, mcp-registry/cloud.theprotocol/registry/theprotocol_oauthIntrospect, mcp-registry/co.ainumbers/tools/validate_mcp_authorization_metadata. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/network.tenzro/tenzro/oauth_discovery down right now?

mcp-registry/network.tenzro/tenzro/oauth_discovery's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fnetwork.tenzro%2Ftenzro%2Foauth_discovery.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fnetwork.tenzro%2Ftenzro%2Foauth_discovery or MCP find_alternatives. Check mcp-registry/network.tenzro/tenzro/oauth_discovery's live status: https://glimind.com/tool/mcp-registry/network.tenzro/tenzro/oauth_discovery.