Agent MCP Directory

Saifs: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Saifs at mcp.saifs.ai 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

CompanySaifs (registry title: Assessment Intelligence)
Domainsaifs.ai
CategoryUncategorised (assigned by this directory from the registry description)
MCP serverSign-in required (OAuth with client registration)
Ora scorenone: Ora returned no cached score for saifs.ai when asked on 5 November 2026
Company found throughthe GitHub MCP Registry; the official MCP Registry
Last verified4 November 2026

MCP server

Endpointhttps://mcp.saifs.ai/mcp
How it was foundlisted in the GitHub MCP Registry; the official MCP Registry
Transportstreamable-http
HTTP status401
Connected4 November 2026, 20:04 UTC
Handshake time1,112 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:18Z https://mcp.saifs.ai/mcp sent initialize result auth-required (HTTP 401) 1397 ms
  • 20:04:21Z https://mcp.saifs.ai/mcp sent initialize result auth-required (HTTP 401) 1112 ms

Authentication

Auth typeOAuth with client registration
What the challenge saidBearer realm="OAuth", resource_metadata="https://mcp.saifs.ai/.well-known/oauth-protected-resource/mcp"
Protected resource metadatamcp.saifs.ai
Authorization server metadatamultiplewords.in
Registration endpointhttps://multiplewords.in/o/register/
Client ID metadata documentssupported

The sign-in route, step by step

  1. Request https://mcp.saifs.ai/mcp without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the protected resource metadata at https://mcp.saifs.ai/.well-known/oauth-protected-resource/mcp to find the authorization server.
  3. Register a client at the registration endpoint https://multiplewords.in/o/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 Saifs. 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 fileNot read: the site's robots.txt disallows the path for this crawler.
WebMCP in the initial HTMLNot checked: the home page was not read by the shared crawl.
MCP discovery fileNot checked: the domain is not in the shared crawl for this edition.
A2A agent cardNot checked: the domain is not in the shared crawl for this edition.
A2A agent card (older path)Not checked: the domain is not in the shared crawl for this edition.
agents.jsonNot checked: the domain is not in the shared crawl for this edition.
OAuth authorization server metadataNot checked: the domain is not in the shared crawl for this edition.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: ai.saifs/assessment-intelligence, ai.saifs/code-execution, ai.saifs/collections-optimizer and 2 more
GitHub MCP RegistryYes
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.