Вход

Ищет технические стандарты (3GPP, IETF) с точностью, позволяет анализировать связи между спецификациями и их содержание.

давно не проверялся схема сломана Удалённый · Streamable HTTP Без авторизации Веб и поиск ИИ и модели Официальный реестр · 9 просмотров

Что умеет

Ищет технические стандарты (3GPP, IETF) с точностью, позволяет анализировать связи между спецификациями и их содержание.

Перевод каталога (LLM) · показать оригинал автора

SpecProof: Search standards specs with MCP-ready precision.

Подключение

Удалённый сервер: клиент обращается по адресу, код на вашей машине не запускается.

Claude Desktop

claude_desktop_config.json

Cursor

~/.cursor/mcp.json

Windsurf

~/.codeium/windsurf/mcp_config.json

Вставьте блок mcpServers в файл конфигурации своего клиента. Ключи не входят в файл: вместо SET_LOCALLY подставьте свои значения.

{
    "mcpServers": {
        "ai-specproof-specproof-mcp": {
            "url": "https://mcp.specproof.ai/"
        }
    }
}

Вызов без установки — через шлюз

Агент вызывает инструменты этого сервера через https://www.n2j.ru/mcphub/mcp: hub_call_tool {"server":"ai-specproof-specproof-mcp","tool":"…","arguments":{…}} Ключ не нужен, но сервер N2J ограничивает частоту анонимных вызовов.

https://mcp.specproof.ai/

Инструменты

17 схем · ≈ 3 013 условных токенов

get_spec_references

Get all specifications referenced by a given spec. Args: spec number: Specification number (e.g., "23.501", "26.230") reference type: Filter by type - "normative", "informative", "inline" (optional)

Показать схему аргументов
{
    "type": "object",
    "title": "get_spec_referencesArguments",
    "required": [
        "spec_number"
    ],
    "properties": {
        "spec_number": {
            "type": "string",
            "title": "Spec Number"
        },
        "reference_type": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Reference Type",
            "default": null
        }
    }
}

get_spec_dependents

Get all specifications that reference a given spec (reverse lookup). Args: spec number: Specification number to find dependents of max results: Maximum results (default: 50)

Показать схему аргументов
{
    "type": "object",
    "title": "get_spec_dependentsArguments",
    "required": [
        "spec_number"
    ],
    "properties": {
        "max_results": {
            "type": "integer",
            "title": "Max Results",
            "default": 50
        },
        "spec_number": {
            "type": "string",
            "title": "Spec Number"
        }
    }
}

get_relationship_graph

Get a relationship graph centered on a specification, expanding N hops. Returns JSON with nodes and edges suitable for graph visualization. Each node includes title, series, working group, and reference counts. Each edge includes source, target, reference type, and count. Args: spec number: Center specification number depth: Number of hops to expand (1-3, default: 1) reference type: Filter by type - "normative", "informative" (optional)

Показать схему аргументов
{
    "type": "object",
    "title": "get_relationship_graphArguments",
    "required": [
        "spec_number"
    ],
    "properties": {
        "depth": {
            "type": "integer",
            "title": "Depth",
            "default": 1
        },
        "spec_number": {
            "type": "string",
            "title": "Spec Number"
        },
        "reference_type": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Reference Type",
            "default": null
        }
    }
}

get_spec_metadata

Get enriched metadata for specifications with filtering. Args: spec number: Filter by spec number (partial match) series: Filter by series (e.g., "26" for 26.xxx codecs) working group: Filter by working group (e.g., "SA4") doc class: Filter by document class - "TS" or "TR" limit: Maximum results (default: 50)

Показать схему аргументов
{
    "type": "object",
    "title": "get_spec_metadataArguments",
    "properties": {
        "limit": {
            "type": "integer",
            "title": "Limit",
            "default": 50
        },
        "series": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Series",
            "default": null
        },
        "doc_class": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Doc Class",
            "default": null
        },
        "spec_number": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Spec Number",
            "default": null
        },
        "working_group": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Working Group",
            "default": null
        }
    }
}

get_most_referenced_specs

Get the most referenced (most important) specifications ranked by incoming reference count. Args: doc type: Filter by "3gpp" or "ietf" series: Filter by series number limit: Maximum results (default: 20)

Показать схему аргументов
{
    "type": "object",
    "title": "get_most_referenced_specsArguments",
    "properties": {
        "limit": {
            "type": "integer",
            "title": "Limit",
            "default": 20
        },
        "series": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Series",
            "default": null
        },
        "doc_type": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Doc Type",
            "default": null
        }
    }
}

get_series_overview

Get an overview of all specification series with document counts, reference statistics, and working group assignments.

Показать схему аргументов
{
    "type": "object",
    "title": "get_series_overviewArguments",
    "properties": []
}

search_specifications

Search across 3GPP, IETF, and Multimedia specification documents using full-text search. Args: query: Search query terms (required) doc type: Filter by document type - "3gpp", "ietf", or "mpeg" (optional) spec number: Filter by specification number (optional) max results: Maximum number of results to return (default: 10, max: 50)

Показать схему аргументов
{
    "type": "object",
    "title": "search_specificationsArguments",
    "required": [
        "query"
    ],
    "properties": {
        "query": {
            "type": "string",
            "title": "Query"
        },
        "doc_type": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Doc Type",
            "default": null
        },
        "max_results": {
            "type": "integer",
            "title": "Max Results",
            "default": 10
        },
        "spec_number": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Spec Number",
            "default": null
        }
    }
}

semantic_search

Perform semantic search using vector embeddings with FAISS acceleration. Args: query: Natural language search query (required) max results: Maximum number of results to return (default: 5, max: 20) similarity threshold: Minimum similarity threshold 0.0-1.0 (default: 0.3) index type: FAISS index type - "hnsw", "ivf", or "flat" (optional, auto-selected)

Показать схему аргументов
{
    "type": "object",
    "title": "semantic_searchArguments",
    "required": [
        "query"
    ],
    "properties": {
        "query": {
            "type": "string",
            "title": "Query"
        },
        "index_type": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Index Type",
            "default": null
        },
        "max_results": {
            "type": "integer",
            "title": "Max Results",
            "default": 5
        },
        "similarity_threshold": {
            "type": "number",
            "title": "Similarity Threshold",
            "default": 0.3
        }
    }
}

get_document_content

Get specific content from a specification document. Args: filename: Document filename (required) page range: Page range like "10-15" or single page "20" (optional) section: Section title filter (optional)

Показать схему аргументов
{
    "type": "object",
    "title": "get_document_contentArguments",
    "required": [
        "filename"
    ],
    "properties": {
        "section": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Section",
            "default": null
        },
        "filename": {
            "type": "string",
            "title": "Filename"
        },
        "page_range": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Page Range",
            "default": null
        }
    }
}

list_documents

List available specification documents. Args: doc type: Filter by document type - "3gpp", "ietf", or "mpeg" (optional) search pattern: Search pattern for spec number or title (optional) limit: Maximum number of results (default: 20, max: 100)

Показать схему аргументов
{
    "type": "object",
    "title": "list_documentsArguments",
    "properties": {
        "limit": {
            "type": "integer",
            "title": "Limit",
            "default": 20
        },
        "doc_type": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Doc Type",
            "default": null
        },
        "search_pattern": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Search Pattern",
            "default": null
        }
    }
}

get_requirements

List normative requirements (RFC 2119 / BCP 14 "shall/should/may" statements) extracted from specifications, each cited back to its source clause. Args: spec number: Filter by spec number, e.g. "23.501" or "RFC 9110" (optional) obligation: Filter by strength - "must", "must not", "should", "should not", or "may" (optional) search: Keyword to search within the requirement text (optional) limit: Maximum number of requirements to return (default: 30, max: 100)

Показать схему аргументов
{
    "type": "object",
    "title": "get_requirementsArguments",
    "properties": {
        "limit": {
            "type": "integer",
            "title": "Limit",
            "default": 30
        },
        "search": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Search",
            "default": null
        },
        "obligation": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Obligation",
            "default": null
        },
        "spec_number": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Spec Number",
            "default": null
        }
    }
}

generate_tests

Generate a cited, runnable conformance test that verifies one normative requirement. The test is grounded in the requirement sentence plus its surrounding clause from the corpus, and every test cites the spec, section and page it enforces. If the requirement is not testable (boilerplate, scope text), the generator abstains rather than inventing a test. Args: requirement id: The requirement's id, as shown by get requirements target: "pytest" for a runnable Python test module, or "gherkin" for a reviewable .feature file (default: pytest)

Показать схему аргументов
{
    "type": "object",
    "title": "generate_testsArguments",
    "required": [
        "requirement_id"
    ],
    "properties": {
        "target": {
            "type": "string",
            "title": "Target",
            "default": "pytest"
        },
        "requirement_id": {
            "type": "integer",
            "title": "Requirement Id"
        }
    }
}

diff_spec_versions

Diff two versions of a specification at the NORMATIVE level: which requirements were added, removed, or reworded. Not a textual diff — a clause that merely moved page or was recased counts as unchanged. Args: spec base: Spec identity without the version, e.g. "38331" or "23501" from version: Older version label, e.g. "j20" (default: the second-newest in the corpus) to version: Newer version label, e.g. "j30" (default: the newest in the corpus) obligation: Only report changes at this strength — "must", "must not", "should", "should not", "may" limit: Max requirements to list per bucket (default

Показать схему аргументов
{
    "type": "object",
    "title": "diff_spec_versionsArguments",
    "required": [
        "spec_base"
    ],
    "properties": {
        "limit": {
            "type": "integer",
            "title": "Limit",
            "default": 25
        },
        "spec_base": {
            "type": "string",
            "title": "Spec Base"
        },
        "obligation": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Obligation",
            "default": null
        },
        "to_version": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "To Version",
            "default": null
        },
        "from_version": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "From Version",
            "default": null
        }
    }
}

get_schema_definitions

Look up formal, machine-checkable structure defined in the specifications: ASN.1 types (3GPP RRC/NAS message grammars) and JSON Schema / OpenAPI models (5G Service Based Interfaces). Prefer this over prose search when the question is about a message's structure — field names, types, ranges, optionality. The definition is returned verbatim from the spec, so it is exact rather than recalled. Args: name: Type or schema name, e.g. "RRCSetup", "MeasConfig", "SmContextCreateData" spec number: Restrict to a spec, e.g. "38.331" kind: "asn1", "openapi" or "json schema" limit: Maximum definitions to ret

Показать схему аргументов
{
    "type": "object",
    "title": "get_schema_definitionsArguments",
    "properties": {
        "kind": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Kind",
            "default": null
        },
        "name": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Name",
            "default": null
        },
        "limit": {
            "type": "integer",
            "title": "Limit",
            "default": 10
        },
        "spec_number": {
            "anyOf": [
                {
                    "type": "string"
                },
                {
                    "type": "null"
                }
            ],
            "title": "Spec Number",
            "default": null
        }
    }
}

get_rfc_lineage

An RFC's revision history. RFCs are immutable — an RFC is never revised, it is obsoleted or updated by a different RFC — so this Obsoletes/Updates graph, not a version diff, IS its change history. Use it to find out whether an RFC you depend on has been superseded. Args: rfc: The RFC, e.g. "7231", "rfc7231" or "RFC 7231"

Показать схему аргументов
{
    "type": "object",
    "title": "get_rfc_lineageArguments",
    "required": [
        "rfc"
    ],
    "properties": {
        "rfc": {
            "type": "string",
            "title": "Rfc"
        }
    }
}

build_cross_spec_suite

Assemble the normative requirements for one procedure across a spec AND the specs it normatively references — a procedure like registration or handover is never described in a single document. Returns a cited suite plan; feed the requirement ids to generate tests. Args: spec base: The anchor spec, e.g. "23502" or "38331" keyword: The procedure/topic, e.g. "registration", "handover", "authentication" include references: Also pull matching clauses from specs this one references (default: True) limit: Max requirements in the plan (default: 20, max: 50)

Показать схему аргументов
{
    "type": "object",
    "title": "build_cross_spec_suiteArguments",
    "required": [
        "spec_base",
        "keyword"
    ],
    "properties": {
        "limit": {
            "type": "integer",
            "title": "Limit",
            "default": 20
        },
        "keyword": {
            "type": "string",
            "title": "Keyword"
        },
        "spec_base": {
            "type": "string",
            "title": "Spec Base"
        },
        "include_references": {
            "type": "boolean",
            "title": "Include References",
            "default": true
        }
    }
}

get_database_stats

Get comprehensive database and system statistics.

Показать схему аргументов
{
    "type": "object",
    "title": "get_database_statsArguments",
    "properties": []
}