# asfo [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/granetb-asfo/asfo  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/asfo

## Description
Agent-to-agent gateway routing tasks to Sherlock, Watson, or Moriarty for one decisive answer.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What asfo MCP server does

The listing describes the asfo MCP server as an agent-to-agent gateway. Its stated purpose is to route tasks to one of three named agents—Sherlock, Watson, or Moriarty—and return one decisive answer. The supplied repository README does not explain how that routing works, what inputs the gateway accepts, or how the result is returned.

The repository material identifies the project as a Next.js application created with `create-next-app`. It refers to editing `app/page.tsx` and viewing the result in a browser. No README section documents an MCP implementation, an MCP transport, a server URL, callable tools, authentication, or connections to external services.

## How it works

No implementation flow is described in the available material. The current description supplies the intended agent-routing concept, but it does not define selection rules for Sherlock, Watson, or Moriarty, task-handling behavior, response formatting, or failure handling. Those details must be confirmed by inspecting the source code.

The documented application behavior is the standard Next.js development workflow: start the project with a package-manager command, then open the local site at `http://localhost:3000`. Changes to `app/page.tsx` are reflected automatically during development.

## Setup and configuration

The README documents four equivalent development commands:

- `npm run dev`
- `yarn dev`
- `pnpm dev`
- `bun dev`

After starting the development server, open `http://localhost:3000` in a browser. The supplied material does not list environment variables, required credentials, production configuration, MCP client configuration, or deployment-specific settings. It mentions Vercel as a deployment option for the Next.js project, but gives no project-specific deployment procedure.

## Tools and capabilities

The asfo MCP server has no documented MCP tool list in the supplied README. The only capability stated by the listing is routing tasks among Sherlock, Watson, and Moriarty to produce one answer. The repository also supports a Next.js page-development workflow, including automatic page updates and font loading through `next/font` with the Geist font family.

Do not infer callable MCP tools, agent APIs, transport support, or integration targets from the project name or listing description alone. The available material does not establish any of those details.

## Limitations and notes

The primary limitation is documentation coverage. The listing presents an agent-routing description, while the README is the default-style documentation for a Next.js application. It does not confirm that the asfo MCP server is implemented, expose its interface, or explain how an MCP client should connect.

Before adopting it, inspect the repository for MCP server entry points, tool definitions, transport setup, and instructions beyond the supplied README. Client compatibility, authentication requirements, licensing, and production readiness are also not specified here.

_Full upstream README: https://allmcps.com/mcp/asfo/readme_