← Index

Banjo

io.github.shatch/banjov0.1.13Other

Self-hosted AI assistant that places real phone calls for you: bookings, reservations, errands.

The current version, v0.1.13, was published to the official MCP registry on 2026-10-17. It is distributed as the Docker image ghcr.io/shatch/banjo:0.1.13, filed under Other by this index, and declares 10 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Banjo in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-11-05 21:03 UTC
screened 2026-10-06tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“Normal capability description”via static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.

That verdict was true at screening time (snapshot 2026-10-19).

Contracts can change after screening, with no version bump. The gate pins Banjo’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for Banjo](https://mcpindex.ai/server/io-github-shatch-banjo) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-shatch-banjo">Independent trust record for Banjo</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-shatch-banjo)](https://mcpindex.ai/server/io-github-shatch-banjo)
HTML
<a href="https://mcpindex.ai/server/io-github-shatch-banjo"><img src="https://mcpindex.ai/api/v1/badge/io-github-shatch-banjo" alt="mcpindex verdict" height="20" /></a>
Environment variables
DATABASE_URL
requiredsecret

Postgres connection URL. Migrations run on boot.

MCP_API_KEY
requiredsecret

Bearer token MCP clients must send (at least 32 characters, e.g. openssl rand -hex 32).

ASSISTANT_PRINCIPAL_NAME
required

The name of the person Banjo calls on behalf of.

PUBLIC_HOSTNAME
required

Public hostname Twilio reaches this server on (no scheme), e.g. a tunnel or reverse proxy.

VOICE_AI_PROVIDER
required

Voice AI vendor. openai is the one carrying live traffic.

OPENAI_API_KEY
secret

OpenAI API key, for VOICE_AI_PROVIDER=openai or openai-live.

TWILIO_ACCOUNT_SID
required

Twilio account SID.

TWILIO_AUTH_TOKEN
requiredsecret

Twilio auth token.

TWILIO_PHONE_NUMBER
required

The Twilio number Banjo calls from, in E.164 (+15551234567).

NOTIFICATION_CHANNEL

How Banjo tells you a call's outcome. twilio_sms also needs NOTIFY_TO_PHONE_NUMBER and NOTIFY_FROM_PHONE_NUMBER; pushover needs PUSHOVER_APP_TOKEN and PUSHOVER_USER_KEY.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Other