← Index

Wafeq

io.github.ohneben/wafeq-mcpv2.0.0Other

Wafeq accounting API: all 251 endpoints as safety-categorized MCP tools, over stdio or HTTP.

The current version, v2.0.0, was published to the official MCP registry on 2026-09-08. It is distributed as the Docker image ghcr.io/ohneben/wafeq-mcp:2.0.0, filed under Other by this index, and declares 6 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 Wafeq 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
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-08).

Contracts can change after screening, with no version bump. The gate pins Wafeq’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

Environment variables
MCP_TRANSPORT
required

Server transport. Set to 'stdio' for local MCP clients; the image otherwise starts the Streamable HTTP transport.

WAFEQ_API_KEY
secret

Private organization API key, sent as `Authorization: Api-Key <key>`. Wafeq -> Settings -> Developer -> API keys. Required unless WAFEQ_ACCESS_TOKEN is set.

WAFEQ_ACCESS_TOKEN
secret

OAuth2 app access token, sent as `Authorization: Bearer <token>`. Use instead of WAFEQ_API_KEY.

WAFEQ_TOOL_GROUPS

Comma-separated resource groups to expose, e.g. invoices,bills,reports. Empty exposes all 251 generated tools.

WAFEQ_API_BASE_URL

Overrides the Wafeq API base URL. Defaults to https://api.wafeq.com/v1

MCP_SHARED_TOKEN
secret

Bearer token required on the /mcp endpoint when running the HTTP transport. Empty leaves the endpoint open, so bind it to localhost only.

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