SpecProof

{
  "id": "aix_c1ba9cbc35",
  "name": "SpecProof",
  "operator": "(unclaimed - source: registry-official · publisher: ai.specproof)",
  "description": "SpecProof: Search standards specs with MCP-ready precision.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-25",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "api-integration",
    "data-enrichment",
    "sql-database"
  ],
  "protocols": {
    "mcp": "https://mcp.specproof.ai/",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 1938,
    "uptime_30d": 0.9956331877729258,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 44,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-25T02:00:59.294Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://specproof.ai/"
    },
    {
      "label": "repository",
      "url": "https://github.com/ibouazizi/specproof.git"
    }
  ],
  "avatar": "https://github.com/ibouazizi.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/ibouazizi"
    }
  ],
  "profile": {
    "mcp_server": "3gpp-spec-server",
    "mcp_version": "1.29.0",
    "tool_count": 17,
    "tools": [
      {
        "name": "get_spec_references",
        "description": "Get all specifications referenced by a given spec.\n\n        Args:\n            spec_number: Specification number (e.g., \"23.501\", \"26.230\")\n            reference_type: Filter by type - \"normative\", \"informative\", \"inline\" (optional)\n        "
      },
      {
        "name": "get_spec_dependents",
        "description": "Get all specifications that reference a given spec (reverse lookup).\n\n        Args:\n            spec_number: Specification number to find dependents of\n            max_results: Maximum results (default: 50)\n        "
      },
      {
        "name": "get_relationship_graph",
        "description": "Get a relationship graph centered on a specification, expanding N hops.\n\n        Returns JSON with nodes and edges suitable for graph visualization.\n        Each node includes title, series, working group, and reference counts.\n        Each edge includes source, target, reference type, and count.\n\n        Args:\n            spec_number: Center specification number\n            depth: Number of hops to expand (1-3, default: 1)\n            reference_type: Filter by type - \"normative\", \"informative\" (optional)\n        "
      },
      {
        "name": "get_spec_metadata",
        "description": "Get enriched metadata for specifications with filtering.\n\n        Args:\n            spec_number: Filter by spec number (partial match)\n            series: Filter by series (e.g., \"26\" for 26.xxx codecs)\n            working_group: Filter by working group (e.g., \"SA4\")\n            doc_class: Filter by document class - \"TS\" or \"TR\"\n            limit: Maximum results (default: 50)\n        "
      },
      {
        "name": "get_most_referenced_specs",
        "description": "Get the most referenced (most important) specifications ranked by incoming reference count.\n\n        Args:\n            doc_type: Filter by \"3gpp\" or \"ietf\"\n            series: Filter by series number\n            limit: Maximum results (default: 20)\n        "
      },
      {
        "name": "get_series_overview",
        "description": "Get an overview of all specification series with document counts, reference statistics, and working group assignments."
      },
      {
        "name": "search_specifications",
        "description": "Search across 3GPP, IETF, and Multimedia specification documents using full-text search.\n\n    Args:\n        query: Search query terms (required)\n        doc_type: Filter by document type - \"3gpp\", \"ietf\", or \"mpeg\" (optional)\n        spec_number: Filter by specification number (optional) \n        max_results: Maximum number of results to return (default: 10, max: 50)\n    "
      },
      {
        "name": "semantic_search",
        "description": "Perform semantic search using vector embeddings with FAISS acceleration.\n    \n    Args:\n        query: Natural language search query (required)\n        max_results: Maximum number of results to return (default: 5, max: 20)\n        similarity_threshold: Minimum similarity threshold 0.0-1.0 (default: 0.3)\n        index_type: FAISS index type - \"hnsw\", \"ivf\", or \"flat\" (optional, auto-selected)\n    "
      },
      {
        "name": "get_document_content",
        "description": "Get specific content from a specification document.\n    \n    Args:\n        filename: Document filename (required)\n        page_range: Page range like \"10-15\" or single page \"20\" (optional)\n        section: Section title filter (optional)\n    "
      },
      {
        "name": "list_documents",
        "description": "List available specification documents.\n    \n    Args:\n        doc_type: Filter by document type - \"3gpp\", \"ietf\", or \"mpeg\" (optional)\n        search_pattern: Search pattern for spec number or title (optional)\n        limit: Maximum number of results (default: 20, max: 100)\n    "
      },
      {
        "name": "get_requirements",
        "description": "List normative requirements (RFC 2119 / BCP 14 \"shall/should/may\" statements)\n    extracted from specifications, each cited back to its source clause.\n\n    Args:\n        spec_number: Filter by spec number, e.g. \"23.501\" or \"RFC 9110\" (optional)\n        obligation: Filter by strength - \"must\", \"must_not\", \"should\", \"should_not\", or \"may\" (optional)\n        search: Keyword to search within the requirement text (optional)\n        limit: Maximum number of requirements to return (default: 30, max: 100)\n    "
      },
      {
        "name": "generate_tests",
        "description": "Generate a cited, runnable conformance test that verifies one normative requirement.\n\n    The test is grounded in the requirement sentence plus its surrounding clause from the\n    corpus, and every test cites the spec, section and page it enforces. If the requirement\n    is not testable (boilerplate, scope text), the generator abstains rather than inventing\n    a test.\n\n    Args:\n        requirement_id: The requirement's id, as shown by get_requirements\n        target: \"pytest\" for a runnable Python test module, or \"gherkin\" for a reviewable\n                .feature file (default: pytest)\n    "
      },
      {
        "name": "diff_spec_versions",
        "description": "Diff two versions of a specification at the NORMATIVE level: which requirements were\n    added, removed, or reworded. Not a textual diff — a clause that merely moved page or was\n    recased counts as unchanged.\n\n    Args:\n        spec_base: Spec identity without the version, e.g. \"38331\" or \"23501\"\n        from_version: Older version label, e.g. \"j20\" (default: the second-newest in the corpus)\n        to_version: Newer version label, e.g. \"j30\" (default: the newest in the corpus)\n        obligation: Only report changes at this strength — \"must\", \"must_not\", \"should\", \"should_not\", \"may\"\n      "
      },
      {
        "name": "get_schema_definitions",
        "description": "Look up formal, machine-checkable structure defined in the specifications: ASN.1 types\n    (3GPP RRC/NAS message grammars) and JSON Schema / OpenAPI models (5G Service Based\n    Interfaces).\n\n    Prefer this over prose search when the question is about a message's *structure* — field\n    names, types, ranges, optionality. The definition is returned verbatim from the spec, so\n    it is exact rather than recalled.\n\n    Args:\n        name: Type or schema name, e.g. \"RRCSetup\", \"MeasConfig\", \"SmContextCreateData\"\n        spec_number: Restrict to a spec, e.g. \"38.331\"\n        kind: \"asn1\", \"openapi"
      },
      {
        "name": "get_rfc_lineage",
        "description": "An RFC's revision history. RFCs are immutable — an RFC is never revised, it is obsoleted\n    or updated by a *different* RFC — so this Obsoletes/Updates graph, not a version diff, IS\n    its change history. Use it to find out whether an RFC you depend on has been superseded.\n\n    Args:\n        rfc: The RFC, e.g. \"7231\", \"rfc7231\" or \"RFC 7231\"\n    "
      },
      {
        "name": "build_cross_spec_suite",
        "description": "Assemble the normative requirements for one procedure across a spec AND the specs it\n    normatively references — a procedure like registration or handover is never described in a\n    single document. Returns a cited suite plan; feed the requirement_ids to generate_tests.\n\n    Args:\n        spec_base: The anchor spec, e.g. \"23502\" or \"38331\"\n        keyword: The procedure/topic, e.g. \"registration\", \"handover\", \"authentication\"\n        include_references: Also pull matching clauses from specs this one references (default: True)\n        limit: Max requirements in the plan (default: 20, max: 50)"
      },
      {
        "name": "get_database_stats",
        "description": "Get comprehensive database and system statistics."
      }
    ],
    "profiled_at": "2026-09-25T02:00:59.294Z"
  },
  "unreachable": false,
  "payment_method": "open"
}