Query only the data you need from your JSON file and keep your context clean
Detailed security scan evidence is not public for this MCP yet. Public identity, registry metadata, and independently observed protocol inventory remain available.
Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.
Version 1.1.0 declares 1 executable entrypoint.
npm install --save-exact json-mcp-filter@1.1.0npx -y -p json-mcp-filter@1.1.0 json-mcp-server{
"mcpServers": {
"json-mcp-filter": {
"command": "npx",
"args": [
"-y",
"-p",
"json-mcp-filter@1.1.0",
"json-mcp-server"
]
}
}
}| Canonical slug | json-filter-mcp-8d2faed8 | Deployment | Local Only |
|---|---|---|---|
| Canonical package | npm:json-mcp-filter | Repository | kehvinbehvin/json-mcp-filter |
| First published | — | Latest release | — |
| Last security verification | — | Classification confidence | 90% |
| Publication | Draft | Official distribution | Not verified |
| Channel | Identifier | Current version | Versions | Source |
|---|---|---|---|---|
| npm | json-mcp-filter | 1.1.0 | 4 | Repository |
| Package | Version | Published / observed | Inventory | Security scan |
|---|---|---|---|---|
| npmjson-mcp-filter | 1.1.0Current | Sep 5, 2026 | 3 toolsSucceeded · 0 resources · 0 prompts | Evidence restricted |
Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.
No public current-version evidence is available yet.
| Tool | Category | Annotations | Risk |
|---|---|---|---|
json_dry_runAnalyze the size breakdown of JSON data using a shape object to determine granularity. Returns size information in bytes for each specified field, mirroring the shape structure but with size values instead of data.Input schema{
"type": "object",
"properties": {
"filePath": {
"type": "string",
"description": "Path to the JSON file (local) or HTTP/HTTPS URL to analyze"
},
"shape": {
"description": "Shape object (formatted as valid JSON) defining what to analyze for size. Use 'true' to get total size of a field, or nested objects for detailed breakdown.\n\nExamples:\n1. Get size of single field: {\"name\": true}\n2. Get sizes of multiple fields: {\"name\": true, \"email\": true, \"age\": true}\n3. Get detailed breakdown: {\"user\": {\"name\": true, \"profile\": {\"bio\": true}}}\n4. Analyze arrays: {\"posts\": {\"title\": true, \"content\": true}} - gets total size of all matching elements\n5. Complex analysis: {\n \"metadata\": true,\n \"users\": {\n \"name\": true,\n \"settings\": {\n \"theme\": true\n }\n },\n \"posts\": {\n \"title\": true,\n \"tags\": true\n }\n}\n\nNote: \n- Returns size in bytes for each specified field\n- Output structure mirrors the shape but with size values\n- Array analysis returns total size of all matching elements\n- Use json_schema tool to understand the JSON structure first"
}
},
"required": [
"filePath"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
json_filterFilter JSON data using a shape object to extract only the fields you want. Provide filePath (local file or HTTP/HTTPS URL) and shape parameters.Input schema{
"type": "object",
"properties": {
"filePath": {
"type": "string",
"description": "Path to the JSON file (local) or HTTP/HTTPS URL to filter"
},
"shape": {
"description": "Shape object (formatted as valid JSON) defining what fields to extract. Use 'true' to include a field, or nested objects for deep extraction.\n\nExamples:\n1. Extract single field: {\"type\": true}\n2. Extract multiple fields: {\"type\": true, \"version\": true, \"source\": true}\n3. Extract nested fields: {\"appState\": {\"gridSize\": true, \"viewBackgroundColor\": true}}\n4. Extract from arrays: {\"elements\": {\"type\": true, \"x\": true, \"y\": true}} - applies to each array item\n5. Complex nested extraction: {\n \"type\": true,\n \"version\": true,\n \"appState\": {\n \"gridSize\": true,\n \"viewBackgroundColor\": true\n },\n \"elements\": {\n \"type\": true,\n \"text\": true,\n \"x\": true,\n \"y\": true,\n \"boundElements\": {\n \"type\": true,\n \"id\": true\n }\n }\n}\n\nNote: \n- Arrays are automatically handled - the shape is applied to each item in the array.\n- Use json_schema tool to analyse the JSON file schema before using this tool.\n- Use json_dry_run tool to get a size breakdown of your desired json shape before using this tool.\n"
},
"chunkIndex": {
"type": "number",
"description": "Index of chunk to retrieve (0-based). If filtered data exceeds 400KB, it will be automatically chunked. Defaults to 0 if not specified."
}
},
"required": [
"filePath"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
json_schemaGenerate TypeScript schema for a JSON file or remote JSON URL. Provide the file path or HTTP/HTTPS URL as the only parameter.Input schema{
"type": "object",
"properties": {
"filePath": {
"type": "string",
"description": "JSON file path (local) or HTTP/HTTPS URL to generate schema from"
}
},
"required": [
"filePath"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — |
| Endpoint | Transport | Authentication | Health | Observed |
|---|---|---|---|---|
| No verified remote endpoint is linked. | ||||
Install the selected package version with: npm install --save-exact json-mcp-filter@1.1.0
JSON Filter MCP Server exposed 3 tools during independent protocol observation, including json_dry_run, json_filter, json_schema.
The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.
Curated product and capability guides containing this catalog record.