Code-Fundi MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

code-fundi-auth-verify

Verify the 6-digit code from your email to complete OTP sign-in and activate the API key for all subsequent tool calls in this session.

Instructions

Complete OTP sign-in (POST /v2/auth/verify). Requires the 6-digit code from the user's email after code-fundi-auth-authenticate. The human user must supply the token — ask them explicitly. On success, activates the API key and configures it in-memory for all subsequent tools in this MCP session. Persist CODEFUNDI_API_KEY in MCP config if the user wants auth to survive restarts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>",
      "token": "<token>"
    },
    "name": "code-fundi-auth-verify"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes	Email address used in the authenticate step
`token`	Yes	6-digit OTP verification code

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jul 31, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses side effects beyond the readOnlyHint=false annotation: 'On success, activates the API key and configures it in-memory for all subsequent tools in this MCP session.' It also advises on persistence for restarts, adding meaningful behavioral context. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core action and endpoint. Every sentence provides essential information: what it does, prerequisite, human involvement, success behavior, and persistence advice. No fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's role in an auth flow, the description covers prerequisites, the human-in-the-loop requirement, success effects, and optional persistence. Without an output schema, it sufficiently addresses what the agent needs to know to execute and handle the outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by linking the token to the email verification step and emphasizing that the human user must supply it, which helps the agent understand where the values come from and how to obtain them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Complete OTP sign-in (POST /v2/auth/verify)'. It specifies the exact action and endpoint, and distinguishes it from sibling tools by referencing the preceding authenticate step and the follow-up activation of API keys.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit usage sequencing: 'Requires the 6-digit code from the user's email after code-fundi-auth-authenticate.' It also instructs the agent to ask the human user for the token and explains the effect of success (activates the API key for the session), giving clear when-to-use context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.