← Index

ImmyBot MCP

io.github.Servosity/immybot-mcpv0.1.8Databases

Every ImmyBot endpoint typed, plus a local SQLite mirror that answers the cross-tenant questions

The current version, v0.1.8, was published to the official MCP registry on 2026-10-16. It is distributed through a declared package, filed under Databases by this index, and declares 9 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 ImmyBot MCP 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
Auditable install path →Watch it hold a drift →
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-10-27 15:48 UTC
screened 2026-08-30tier: scannedgranularity: description-levelsource: registry

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

mcpindex.integrity.descriptionpassINFO

evidence“No malicious instructions”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
  • - Still current: the description we screened is unchanged, re-checked against the registry
  • - 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-20).

Contracts can change after screening, with no version bump. The gate pins ImmyBot MCP’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 ImmyBot MCP](https://mcpindex.ai/server/io-github-servosity-immybot-mcp) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-servosity-immybot-mcp">Independent trust record for ImmyBot MCP</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-servosity-immybot-mcp)](https://mcpindex.ai/server/io-github-servosity-immybot-mcp)
HTML
<a href="https://mcpindex.ai/server/io-github-servosity-immybot-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-servosity-immybot-mcp" alt="mcpindex verdict" height="20" /></a>
Environment variables
IMMYBOT_BASE_URL

Full API base URL. Leave blank: the CLI builds it from IMMYBOT_SUBDOMAIN. Set it only to point at a different host.

IMMYBOT_CLIENT_ID
requiredsecret

Set the IMMYBOT_CLIENT_ID credential for the ImmyBot MCP server.

IMMYBOT_CLIENT_SECRET
requiredsecret

Set the IMMYBOT_CLIENT_SECRET credential for the ImmyBot MCP server.

IMMYBOT_SUBDOMAIN
required

Set the IMMYBOT_SUBDOMAIN credential for the ImmyBot MCP server.

IMMYBOT_TENANT_ID
required

Set the IMMYBOT_TENANT_ID credential for the ImmyBot MCP server.

IMMYBOT_TOKEN_URL

Token endpoint the client-credentials exchange posts to. Leave the prefilled default unless your tenant uses a different token endpoint.

IMMYBOT_USER_AGENT

Overrides the User-Agent the CLI sends on ImmyBot requests. Leave blank to use the CLI's own built-in User-Agent.

PRINTING_PRESS_CLIENT_PROFILE

Binds this MCP server to one tenant-gated client profile, so every call answers for that customer. Leave blank to use the profile configured as default_client_profile.

IMMYBOT_NO_CONFIG_WRITE

Set to 1 to keep credentials off disk. The token cache becomes a no-op, so the connector mints a fresh token each run instead of writing one to config.toml. Leave blank for the default cached behaviour.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Databases
briq
cloud.briq/briq

Give your agent its own cloud: Postgres, Redis, a sandbox or any Docker image, in one MCP call.

Neon
com.neon/mcp

Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.

IT Glue MCP
io.github.Servosity/itglue-mcp

Every IT Glue resource, plus an offline SQLite mirror, fleet-wide cross-resource search, and