MCP Listings

MCP has a fast-moving ecosystem. Treat public listings as discovery tools, not as trust signals. Review the server source, permissions, maintenance state, and credential scope before adding it to a Facio runtime.

Listings and directories

Evaluation checklist

• Is the server source public and maintained?
• Does it run local code through stdio, or call a hosted endpoint?
• Which account scopes does it request?
• Can credentials be passed through env or headers with ${credentials.KEY} placeholders?
• Does the server expose destructive tools such as delete, write, deploy, send, or purchase?
• Should enabledTools narrow the available tools instead of ['*']?
• Should tool policy require approval for this server's tools?

Safer first configuration

For high-impact servers, start with a narrow tool list:

{
  "enabledTools": ["search", "read", "list"]
}

After the first audit review, expand tool access only when the workflow needs it.