"Tools and Systems for Math, AI, and Proof Verification with Bug Detection and Auto Fixing" matching MCP tools:

• thinkneo_get_proof

  ThinkNEO Control Plane

  Retrieve the immutable proof record for a verified claim. Includes the original claim, verification evidence, verifier identity, and a SHA-256 proof hash for tamper detection. This is the 'proof' in 'From Prompt to Proof'. Requires authentication.

  Connector

• designesy_readiness_score

  Designesy

  Score a URL for design-system AI readiness — the 6th maturity axis (zeroheight 2026). 10 checks probe the target origin for machine-readable artifacts: DTCG token files, llms.txt, agent.json, MCP endpoint (tools/list), DESIGN.md, token $description, component schemas, sitemap.xml, robots.txt, and Open Graph/Twitter meta. Use this to verify whether a design system is the default context AI tools build from, or whether AI is silently working around it. When NOT to use: for full design-contract scoring, use designesy_score; for AI-drift detection, use designesy_drift_score. Executable — fetches the URL and probes the origin via HEAD/GET for each artifact. No browser needed. Returns JSON: { ok, url, score (0-100), grade (A-F), pass, warn, fail, total, checks[{id, item, category, status, detail}] }. Results cached ~24h per URL.

  Connector

• Zephex_dev_info

  Zephex

  Expert developer playbooks — not your repo. Stripe webhooks & checkout, Supabase RLS, Next.js auth (clerk, next-auth), payment flows, CSP/HSTS, deploy patterns. operation=search finds entries by question; operation=get returns full guidance by slug from search. Read summary and checklist first. 2 credits hosted. No project path. Call when standard patterns beat guessing — wiring stripe checkout, fixing auth middleware, Supabase RLS policies, hardening after audit_headers. Use AFTER repo tools if code context is still thin. NOT for user's codebase (get_project_context, find_code, read_code), registry packages (check_package), tests (check_test), live URL (audit_headers), or saving decisions (project_memory). Example: Zephex_dev_info({ operation: 'search', query: 'Stripe webhook raw body verification', category: 'payments' }) then get with returned slug. Read-only.

  Connector

• get_wallet_summary

  mcp-server

  Call this whenever the user asks for a wallet summary, wallet list, their wallets, wallet balances, verified holdings, or Proof of Funds ceiling. Returns all wallets for the authenticated user with their balances, verification status, and Proof of Funds ceiling. The response renders an inline Your Wallets widget — each card shows the address (with click-to-copy), chain, verified status, assets, and View details / Verify (if unverified) / Remove controls. Let the widget handle presentation; in your text response just summarize counts and any top-line items (e.g. "You have 3 wallets, 2 verified, POF ceiling $65k"). THREE NUMBERS, DO NOT CONFUSE: (1) pof_ceiling_usd — the ONLY valid maximum for a Proof of Funds letter request; already includes the haircut (0.98× stablecoins, 0.935× volatile) and excludes unverified wallets. (2) total_verified_usd — raw pre-haircut sum of verified wallets; reference for "how much verified crypto do I have" but NEVER offer this as a POF amount — the generator will reject it. (3) Σ wallets[].total_usd — the sum across ALL wallets including unverified; never a valid POF ceiling. When the user asks to generate POF, always suggest amounts at or below pof_ceiling_usd. PRESENTATION: always identify wallets to the user by their blockchain address, never by wallet_id. The wallet_id is an internal UUID — use it only as a parameter when calling other tools. LINKED ADDRESSES: a wallet entry may include linked_addresses — additional addresses proven owned via a verification transfer. ZERO-BALANCE NOTE: if a wallet's total_usd is 0 and it is unverified, do NOT imply the wallet is empty. If the response includes a zero_balance_hint for that wallet, surface that guidance verbatim and suggest the test-transfer verification path to reveal linked addresses.

  Connector

• glim_detect_ai

  glim.sh

  Detect AI-generated text. Scores any text for AI-authorship likelihood and returns an overall verdict (AI / human / mixed) with confidence, the AI/human/AI-assisted fractions, and a segment-by-segment breakdown showing exactly which parts read as AI-written. Use it to verify whether content (comments, articles, profiles) is AI-generated, or to check text before publishing to see which segments would trip AI detectors - revise the flagged segments and re-check. tier='premium' uses the most accurate detection class, additionally flags humanized text (AI output run through paraphrasing/'humanizer' tools), and is substantially more robust to evasion, at ~10x the price of 'standard'. Cost scales with text length: ~$0.06 per 1,000 words standard, ~$0.60 premium; minimum $0.06. Texts under ~100 words are automatically analyzed with the premium class at the standard price.

  Connector

• malware_get_template

  website-search

  Get Lenny Zeltser's malware analysis report template. The report covers Executive Summary, Sample Snapshot, Malware Family Identification, Component Inventory, Runtime Requirements, Sources, Capabilities, Indicators of Compromise, Analysis Details, What We Don't Know, optional Infection Vector, optional Detection Engineering, About this Report, Appendix: Analysis Environment, and optional Appendix: Analysis Scripts. This server never requests your sample, analysis notes, or indicators and instructs your AI to keep them local—guidelines and the report template flow to your AI for local analysis.

  Connector

• thinkneo_verify_claim

  ThinkNEO Control Plane

  Trigger verification of a registered action claim. Runs the appropriate verification adapter (HTTP check, file check, database check, etc.) and returns the result with evidence. If already verified, returns cached result (use force=true to re-verify). Part of the Outcome Validation Loop — 'From Prompt to Proof'. Requires authentication.

  Connector

• get_account_status

  mcp-server

  Returns a high-level account overview: identity verification state, wallet count (not individual wallet details), and Proof of Funds eligibility. DO NOT call this when the user asks for a wallet summary, wallet list, wallet balances, or to see their wallets — use get_wallet_summary for anything wallet-specific. This tool is for answering "is my account ready?"-style questions.

  Connector

• check_action

  icme-preflight

  Enforce a guardrail: verify an agent action against a compiled policy using formal verification. An SMT solver — not an LLM — determines whether the action satisfies every rule. Returns SAT (allowed) or UNSAT (blocked) with extracted values and a cryptographic ZK proof that the check was performed correctly. Cannot be jailbroken. 1 credit ($0.01). Requires api_key. Tip: end the action with an explicit claim like 'I assert this complies with the policy' for best extraction.

  Connector

• quick_check

  icme-preflight

  Fast yes/no guardrail verdict — returns only ALLOWED or BLOCKED with no proof details. Use when you need a lightweight gate and don't need the full SAT/UNSAT report or ZK proof. Same formal verification under the hood, just a minimal response. 1 credit. Requires api_key.

  Connector

• axiorank_author_detector

  AxioRank: Zero-Trust for AI Agents

  Describe a risk in plain English and AxioRank's AI proposes a custom content detector (regex or keyword) and SAVES it DISABLED for your review. An LLM never arms detection unattended. Outbound content categories only (secret/pii/destructive/injection/egress). Requires the `policies:write` scope and an AI-assessments-enabled plan (Team+).

  Connector

• forcedream_verify_proof

  mcp-server

  Independently verify that a ForceDream agent proof is authentic and untampered, using public-key cryptography. Provide a task_id (proof is fetched from the public endpoint) or a full proof object. Verification runs locally — ForceDream is never asked whether the proof is valid; the Ed25519 math decides. No account or key needed.

  Connector

• tr_validate

  Temsor API — Turkey & EU business data

  Validates Turkish national ID, tax number, IBAN, licence plate, IMEI and barcodes from one endpoint, with type auto-detection. Goes past a yes/no: resolves the bank behind an IBAN, the province behind a licence plate and the GS1 country prefix behind a barcode. Pure local computation — no upstream service is called, so latency is microseconds and the answer never changes for the same input.

  Connector

• intelligence.contagion

  DPX — Institutional Cross-Border Settlement

  Contagion Intelligence — simulates how a macro or financial shock spreads through 30 nodes across 6 domains (financial systems, real economies, commodity networks, policy anchors, social systems, physical infrastructure) using an epidemiological R-value model. Returns system R trajectory, per-epoch spread map, superspreader nodes, containment forecast, and AI briefing. R < 1.0 = self-limiting; R ≥ 1.0 = expanding. Call /contagion/nodes first to discover valid origin IDs. POST with origin and magnitude.

  Connector

• axint.repair

  Axint

  Plan a project-aware Apple repair for existing apps. Indexes the local project, classifies build/UI/runtime evidence, runs Cloud Check when source is provided, ranks likely SwiftUI/App files, returns a host-aware patch/proof plan, and writes .axint/repair plus a privacy-safe .axint/feedback packet. Use: use for existing app bugs with logs, UI symptoms, or runtime evidence; not for greenfield generation. Inputs: describe the observed bug and attach logs or evidence; modifiedFiles and project index narrow the plan. Effects: writes .axint/repair and privacy-safe .axint/feedback artifacts; reads local project files.

  Connector

• check_action

  icme-preflight-mcp

  Enforce a guardrail: verify an agent action against a compiled policy using formal verification. An SMT solver — not an LLM — determines whether the action satisfies every rule. Returns SAT (allowed) or UNSAT (blocked) with extracted values and a cryptographic ZK proof that the check was performed correctly. Cannot be jailbroken. 1 credit ($0.01). Requires api_key. Tip: end the action with an explicit claim like 'I assert this complies with the policy' for best extraction.

  Connector

• start_domain_verification

  EmailMCP

  Begin a domain-verification window: temporarily set the target domain's MX to verify.setip.io, start (or reuse) the EmailMCP SMTP receiver on :25, and forward any inbound mail for *@domain to forward_to so a human can grab a verification code from the provider (Apple/Google/etc). Auto-tears down after ttl_minutes.

  Connector

• x402_protected_call

  paycrow

  Make an HTTP API call with manual escrow protection. Full control over verification and timelock parameters. For most payments, use safe_pay instead — it auto-configures protection based on seller trust. Use x402_protected_call when you need: - Custom JSON Schema verification (not just "valid JSON + 2xx") - Hash-lock verification (exact response match) - Specific timelock durations - To override safe_pay's trust-based amount limits

  Connector

• format_auto

  Caliper

  Auto-detect geometry file format and extract metadata statistics. Accepts a 3D geometry file via URL or base64 and returns structured metadata: bounding boxes, triangle counts, manifold analysis, point cloud statistics, and more. This is a read-only analysis tool — it does not perform mesh repair, format conversion, or boolean operations. Supported formats: STL, OBJ, PLY, PCD, LAS/LAZ, glTF/GLB. STEP and IGES support is planned. Provide either file_url (preferred for large files) or file_b64 (for files under 200KB). Include filename for format detection if using file_b64. When using file_url, the format is detected from the URL path extension; filename is not required. Files under 150KB are free. Larger files cost $0.02/MB via x402 (USDC on Base) or card via MPP (Stripe; adds $0.35 surcharge). If payment is required, the response includes payment details. Retry with the payment argument containing the payment proof. Privacy policy: https://caliper.fit/privacy

  Connector

• search_category

  Loppee

  Local category discovery requires current or Home with kind=saved_exact. Provided city/ZIP, coarse Home, and provider IP return no results with commercial_influence=none and record no impressions. Other agent personas cannot access customer location authority and therefore cannot run this local category lane. Local category discovery and recommendations require a current precise location proof or handoff, or a saved_exact Home location. City/state, ZIP, provider IP, saved_coarse locations, and caller-supplied coordinates are neutral area context for business-name disambiguation only: they return no local category or recommendation results, cannot activate Sponsored placement, and record no impressions. Exact and genuine-prefix business-name lookup remains universal; without precise location it is commercially neutral. Exposure-plan payment changes discovery reach and, when Sponsored ordering is active, labeled position-weighted exposure only within the same verification class and verified-review reputation band. It never changes business-profile publication, verification, review authority, reputation, moderation, class ordering, or reputation band. Loppee Jobs is a separate optional paid product; its billing affects job-posting activation only and never business verification or directory ranking.

  Connector