Agent MCP Directory

Rulebase: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Rulebase at mcp.rulebase.co answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.

Fact sheet

CompanyRulebase
Domainrulebase.co
CategoryCommunication & Support (Ora leaderboard category)
MCP serverSign-in required (OAuth with client registration)
Ora score66, grade C; Ora scanned the domain on 23 September 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for rulebase.co, a vendor-published score)
Company found throughOra's public leaderboard
Last verified4 November 2026

MCP server

Endpointhttps://mcp.rulebase.co/mcp
How it was foundlisted in Ora's public leaderboard
Transportstreamable-http
HTTP status401
Connected4 November 2026, 20:04 UTC
Handshake time1,835 ms over 1 attempt

The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:59:16Z https://mcp.rulebase.co/mcp sent initialize result auth-required (HTTP 401) 1971 ms
  • 20:04:19Z https://mcp.rulebase.co/mcp sent initialize result auth-required (HTTP 401) 1835 ms

Authentication

Auth typeOAuth with client registration
What the challenge saidBearer error="unauthorized", error_description="Authorization needed", scope="openid email offline_access", resource_metadata="https://mcp.rulebase.co/.well-known/oauth-protected-resource"
Protected resource metadatamcp.rulebase.co
Authorization server metadataauth.rulebase.co
Registration endpointhttps://auth.rulebase.co/oauth2/register
Client ID metadata documentssupported

The sign-in route, step by step

  1. Request https://mcp.rulebase.co/mcp without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the protected resource metadata at https://mcp.rulebase.co/.well-known/oauth-protected-resource to find the authorization server.
  3. Register a client at the registration endpoint https://auth.rulebase.co/oauth2/register (dynamic client registration), so no human has to create an app first.
  4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for Rulebase. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNo OpenAPI file at the root paths checked.
WebMCP in the initial HTMLNot detected on the home page by the shared crawl.
MCP discovery fileNot found (the crawl got a non-200 answer).
A2A agent cardNot found (the crawl got a non-200 answer).
A2A agent card (older path)Not found (the crawl got a non-200 answer).
agents.jsonNot found (the crawl got a non-200 answer).
OAuth authorization server metadataNot found (the crawl got a non-200 answer).
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: co.rulebase/rulebase
GitHub MCP RegistryNo
awesome-remote-mcp-serversNo
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.