# codeitall MCP server

Behavioral oracle for Rust crate APIs: runtime behavior, yank/advisory, deprecation, sig search

## Links
- Registry page: https://www.getdrio.com/mcp/dev-codeitall-codeitall
- Repository: https://github.com/codeitalldev/codeitall
- Website: https://api.codeitall.dev/for-ai-agents.html

## Install
- Endpoint: https://api.codeitall.dev/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://api.codeitall.dev/mcp

## Tools
- answer_api_question - Use this when an agent asks open-ended Rust API questions like 'how do I parse a duration string', 'which crate gives me HMAC verification', 'is this function deprecated', 'what's the current way to do JWT auth', or 'compare base64 crates'. Hand off free-text questions verbatim; the substrate routes them deterministically via rule-based intent detection (no LLM in the request path) and dispatches into signature_search, behavior_lookup, compare_implementations, or find_modern_equivalent as appropriate, falling back to bge-m3 cosine retrieval if no rule matches. Returns a structured verdict with routed_via, the primary recommendation, evidence, and caveats. Endpoint: https://api.codeitall.dev/mcp
- signature_search - Use when the agent already knows the signature shape it wants — e.g. `fn(&str) -> Result<Vec<u8>, _>`, `fn(&[u8]) -> Result<String, std::str::Utf8Error>`, or `impl Iterator<Item=Result<...>>`. Returns ranked candidate functions with the crate they live in, downloads, yank status, and a compact behavior summary if probed. Pass the exact signature verbatim; the substrate normalises whitespace + identifiers on its end. Endpoint: https://api.codeitall.dev/mcp
- behavior_lookup - Use when the agent has a specific (crate, fn_name) pair and wants to know what inputs it actually accepts at runtime — e.g. `(crate='jiff', fn_name='Timestamp::from_str')`. Returns the probe observation table verbatim from the substrate: each row is (input, outcome=ok|err|panic, value or error variant). Pass an optional `inputs` array to filter to specific input strings. The substrate's discrimination findings live here — runtime behaviour the docs are silent or wrong about. Endpoint: https://api.codeitall.dev/mcp
- compare_implementations - Use when the agent asks about a task category — e.g. 'how do I parse JSON in rust', 'compare base64 crates', 'which datetime library handles RFC 3339 timezones right' — and wants the cross-implementation behavior table. The substrate returns side-by-side observations on the canonical input set: for each implementation (crate, fn_name), each input in the family's input set is paired with the observed (outcome, value_or_error_variant). Discrimination signal lives here — the docs-silent runtime behaviour pattern Guiding Principle #8 names. Endpoint: https://api.codeitall.dev/mcp
- find_modern_equivalent - Use when the agent suspects the code it's about to write uses a deprecated API — e.g. `tokio::Runtime::new()` (now `tokio::runtime::Runtime::new()`), `chrono::DateTime::from_str` (now feature-gated), or any path that points to a yanked or RustSec-advisory'd crate version. The substrate returns the current canonical alternative with a behavior summary if probed, and surfaces yank-status / advisory rows verbatim. Endpoint: https://api.codeitall.dev/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: dev.codeitall
- Version: 0.1.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 27, 2026
- Source: https://registry.modelcontextprotocol.io