io.github.aryanduntley/aifp
io.github.aryanduntley/aifp
Is the io.github.aryanduntley/aifp MCP server down? Yes. It has given no valid answer since 2026-10-20: not found.
Database-driven FP enforcement and project management for AI-maintained codebases
not found down since 2026-10-20 · probed 2026-11-14 · unchanged since 2026-10-27
error: No solution found when resolving dependencies cause: Because aifp was not found in the package registry and you require aifp==0.1.1, we can conclude th
- Run it
- uvx aifp@0.1.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/aryanduntley/AIFP
- Registry
- active, updated 2026-02-12 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.artgas1/xmlriver-mcp · alive
- io.github.arun250492/Personal-MCP · needs mcp<2
- DICOM Agent io.github.arunmk-ms/dicom-agent-mcp · alive
- 2Captcha MCP io.github.aruxojuyu665/twocaptcha-mcp · needs env
- AIMFP io.github.aryanduntley/aimfp · alive
- pgops io.github.arzharch/pgops-mcp · crashed on start
- io.github.ascript-cn/ascript-mcp · crashed on start
- verify-atom io.github.asherengos/verify-atom · alive
Servers that mention aifp or enforcement or maintained.
- io.github.wjabanjj/aifp-mcp · alive
- ai.argushq/enforcement-database · no DNS
- Content Sweep ai.contentsweep/agent-access · alive
- Fullmakt ai.fullmakt/fullmakt · needs auth
- Regulations.ai — Global AI Law Tracker ai.regulations/regulations-ai · alive
- Sato Hub: Build Onchain & Crypto Agents ai.satohub/onchain-agents · alive
- Court Rules app.courtrules/court-rules · needs auth
- EuroComply — EU Regulatory Compliance app.eurocomply/compliance · alive
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
- No valid answer since 2026-10-20, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.