ai.saifs/financial-anomaly
Financial Fraud & Anomaly Detection
Is the Financial Fraud & Anomaly Detection MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Flag unusual ledger entries, possible fraud and earnings manipulation for human review.
needs auth probed 2026-11-15 · unchanged since 2026-11-14 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","error_description":"Missing or invalid authorization header"}- Endpoint
- https://financial-anomaly-mcp.saifs.ai/mcp (streamable-http)
- Host
- financial-anomaly-mcp.saifs.ai
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://financial-anomaly-mcp.saifs.ai/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server multiplewords.in, PKCE S256, grants authorization_code, client_credentials, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes read write.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/Saify-Technologies/saifs-ai-mcps-docs
- Website
- https://saifs.ai
- Registry
- active, updated 2026-11-13 · registry entry
Compare this server with others.
More servers
Servers that mention financial.
- AkkruData ai.akkrudata/akkrudata · needs auth
- Balanços.AI ai.balancos/mcp · needs auth
- Constellation Credit ai.constellationfinance/constellation-finance-mcp · needs auth
- Distilla ai.distilla/mcp · needs auth
- Drillr — The financial MCP for AI agents ai.drillr/drillr · alive
- FinanceGenius.AI ai.financegenius/financegenius · alive
- PipeLedger ai.pipeledger/pipeledger · needs auth
- ROIC.AI Financial Data ai.roic/roic · needs auth
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
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.