Skip to content

MCP servers › io.github.BBrunoEsteves › mcp-for-openfilters

MCP server · registry snapshot 2026-11-07 · last tested 2026-11-20

mcp-for-openfilters MCP server

Registry name io.github.BBrunoEsteves/mcp-for-openfilters

by BBrunoEsteves · GitHub account (the registry's namespace rule)repository: same ownerSource ↗PyPI ↗

Design, simulate and optimize optical thin-film coatings with the OpenFilters engine. — the publisher's description

7 of 8 record checks metRead-only · tools listed 2026-11-20version 0.2.2PythonGPL-2.0-or-laterstandard input/output28 tools

Summary

io.github.BBrunoEsteves/mcp-for-openfilters is a local MCP server listed in the official MCP registry at version 0.2.2, under the namespace of the GitHub account BBrunoEsteves. Its linked repository, github.com/BBrunoEsteves/mcp-for-openfilters, belongs to the same GitHub account. On 2026-11-20 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 28 tools, 9 resources and 5 prompts.

Record checks

7 of 8 record checks met · 1 does not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • #2,679 of 20,725 packages by monthly downloads, tied with 4 others
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
PyPI · listed version current
License
GPL-2.0-or-later
Dependencies
no known high or critical advisories
Repository
public
Tools
28
Last tested
2026-11-20

Tool list at the three APIs

Not sent yet for this version (0.2.2).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-20
Mode
read-only (no tool calls)
Latest version
0.2.2, published 2026-11-06 (registry, as of the 2026-11-07 snapshot)
First listed version
2026-11-06 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-11-06; 2 in the 90 days before the 2026-11-07 snapshot.
Most recent 2 versions
  • 0.2.2 · 2026-11-06
  • 0.2.1 · 2026-11-06
(versions still listed in the registry only)
Registry data
snapshot 2026-11-07
Package and repository
checked 2026-11-19
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-06, listed on 2026-11-07 with version 0.2.2 (published 2026-11-06).

Source: the official MCP Registry list on 2026-11-06 and on 2026-11-07.

What it is

What does this server offer?

Observed inventory
28tools
9resources
5prompts

None of its 28 tools are described as changing anything. For 28 the reading was uncertain, so no mark is shown.

  • “Version, build (git commit of a source checkout, and when this server started: a server started before a code change still runs the old code until the app is restarted), data folder, worker count and…”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • list_materialson 15 other servers

    “List available materials (built-in OpenFilters library plus the user's own) with n,k at a few wavelengths.”

    Publisher declares: read-only yes · open-world no

    1 input
    • name_filterstring or null
  • get_material_index

    “Tabulate n and k of a regular material over wavelengths (default 300-2000 nm, 50 nm steps).”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • namestringrequired
    • wavelengthsobject or array or null“{"from": 380, "to": 1100, "step": 1} or an explicit list of wavelengths (nm).”
    • plotboolean
  • add_materialon 1 other server

    “Add a material to the user's material folder.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    10 inputs, 2 required
    • namestringrequired
    • modelstringrequired
    • descriptionstring
    • nnumber or null
    • knumber
    • coefficientsarray or null
    • tablearray or null
    • table_filestring or null
    • wavelength_unitstring
    • overwriteboolean
  • remove_material

    “Delete one of the user's own materials (from add_material or import_refractiveindex_material).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • namestringrequired
  • search_refractiveindex

    “Search the refractiveindex.info database of optical constants (public domain) by material name, formula or author, e.g.”

    Publisher declares: read-only yes · open-world yes

    4 inputs, 1 required
    • querystringrequired
    • shelfstring or null
    • limitinteger
    • refreshboolean
  • import_refractiveindex_material

    “Download one refractiveindex.info entry (`page` from search_refractiveindex) and add it to the user's materials as an n,k table, usable in designs like any other material.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    6 inputs, 1 required
    • pagestringrequired
    • namestring or null
    • from_nmnumber or null
    • to_nmnumber or null
    • overwriteboolean
    • plotboolean
  • describe_design

    “Validate a design and list its layers (thickness, index and QWOT at the center wavelength; graded layers: number of steps, index range, first and last index, optical thickness), total thickness, the …”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • plot_index_profileboolean
  • compute_spectrum

    “Compute R, T, A, OD, phase, GD or GDD spectra (quantity names R, T, A, OD, R_phase, T_phase, R_GD, T_GD, R_GDD, T_GDD) versus wavelength for one design at one or more angles and polarizations.”

    Publisher declares: read-only yes · open-world no

    10 inputs, 1 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • quantitiesarray
    • wavelengthsobject or array or null“{"from": 380, "to": 1100, "step": 1} or an explicit list of wavelengths (nm).”
    • anglesarray
    • polarizationsarray
    • reverseboolean
    • sample_pointsinteger
    • thresholdobject or null“{"above": 0.999} or {"below": 0.01}: ranges where each series is above/below the level, edges interpolated (e.g.”
    • plotboolean
    • save_csvboolean
  • compute_angle_scan

    “R/T/A (or phase) versus angle of incidence at a single wavelength.”

    Publisher declares: read-only yes · open-world no

    8 inputs, 2 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • wavelengthnumberrequired
    • quantitiesarray
    • anglesobject“{"from": 0, "to": 85, "step": 1}”
    • polarizationsarray
    • sample_pointsinteger
    • thresholdobject or null“as in compute_spectrum, over angle”
    • plotboolean
  • compute_color

    “Color of the coating in reflection or transmission: XYZ, xy, L*a*b*, LCh, sRGB and hex, at each angle (use several angles to see the color shift).”

    Publisher declares: read-only yes · open-world no

    6 inputs, 1 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • anglesarray
    • modestring
    • polarizationstring or number“"s", "p", "unpolarized", or a polarization angle psi in degrees from 0 to 90 (as in the OpenFilters dialogs: R = sin^2(psi) Rs + cos^2(psi) Rp; 0 = p, 90 = s, …”
    • illuminantstring
    • observerstring
  • compute_electric_field

    “Standing-wave |E|^2 inside the coating (relative to the incident wave), e.g.”

    Publisher declares: read-only yes · open-world no

    5 inputs, 2 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • wavelengthnumberrequired
    • anglenumber
    • polarizationstring or number“"s", "p", "unpolarized", or a polarization angle psi in degrees from 0 to 90 (as in the OpenFilters dialogs: R = sin^2(psi) Rs + cos^2(psi) Rp; 0 = p, 90 = s, …”
    • plotboolean
Show 16 more tools
  • compute_monitoring_curves

    “Optical monitoring signal (R or T) versus deposited thickness, as seen during deposition.”

    Publisher declares: read-only yes · open-world no

    8 inputs, 2 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • wavelengthsarray or object or stringrequired“Monitoring wavelengths: a list (e.g.”
    • anglenumber
    • polarizationstring or number“"s", "p", "unpolarized", or a polarization angle psi in degrees from 0 to 90 (as in the OpenFilters dialogs: R = sin^2(psi) Rs + cos^2(psi) Rp; 0 = p, 90 = s, …”
    • modestring
    • directionstring
    • save_mapboolean
    • plotboolean
  • thermal_sensitivity

    “How the peak of R or T nearest `near` (default the center wavelength; e.g.”

    Publisher declares: read-only yes · open-world no

    7 inputs, 1 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • nearnumber or null
    • quantitystring
    • thermalobject or null
    • windowobject or null“Where to look for the peak first, {"from": 507, "to": 557, "step": 0.05}; default near +/- 25 nm.”
    • anglenumber
    • polarizationstring or number“"s", "p", "unpolarized", or a polarization angle psi in degrees from 0 to 90 (as in the OpenFilters dialogs: R = sin^2(psi) Rs + cos^2(psi) Rp; 0 = p, 90 = s, …”
  • thermal_sweep

    “The peak of R or T nearest `near` at each temperature change delta_T (K, relative to the temperature the design's materials and thicknesses describe), with every material's dn/dT, dk/dT and thickness…”

    Publisher declares: read-only yes · open-world no

    9 inputs, 3 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • delta_Tarrayrequired
    • thermalobjectrequired“Thermal properties: {"materials": {"TiO2": {"dn_dT": -1e-4, "cte": 5e-6, "poisson": 0.27, "dk_dT": 0}, "SiO2": {"dn_dT": 1e-5, "cte": 0.5e-6, "poisson": 0.17}}…”
    • nearnumber or null
    • quantitystring
    • windowobject or null“Where to look for the peak first, {"from": 507, "to": 557, "step": 0.05}; default near +/- 25 nm.”
    • anglenumber
    • polarizationstring or number“"s", "p", "unpolarized", or a polarization angle psi in degrees from 0 to 90 (as in the OpenFilters dialogs: R = sin^2(psi) Rs + cos^2(psi) Rp; 0 = p, 90 = s, …”
    • plotboolean
  • evaluate_designon 2 other servers

    “Merit (chi^2, OpenFilters' definition) of a design against targets, with per-target pass fraction and maximum deviation.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 2 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • targetsarrayrequired“Targets, each {"kind": "R"|"T"|"A"|"R_phase"|"T_phase"|"R_GD"|"T_GD"|"R_GDD"|"T_GDD", "angle": 0, "polarization": "unpolarized"|"s"|"p" or an angle psi in degr…”
    • plotboolean
  • layer_sensitivity

    “Change in merit (delta_chi2) and in worst margin when each layer thickness changes by +/- relative_step (default 1 %; the worse direction), to find the layers that need the tightest deposition contro…”

    Publisher declares: read-only yes · open-world no

    3 inputs, 2 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • targetsarrayrequired“Targets, each {"kind": "R"|"T"|"A"|"R_phase"|"T_phase"|"R_GD"|"T_GD"|"R_GDD"|"T_GDD", "angle": 0, "polarization": "unpolarized"|"s"|"p" or an angle psi in degr…”
    • relative_stepnumber
  • optimize_designon 1 other server

    “Optimize a design with OpenFilters: method "refine" (thicknesses only), "needle" (refine and insert new layers until no improvement) or "step" (graded/step index, needs a mixture material).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    5 inputs, 2 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • targetsarrayrequired“Targets, each {"kind": "R"|"T"|"A"|"R_phase"|"T_phase"|"R_GD"|"T_GD"|"R_GDD"|"T_GDD", "angle": 0, "polarization": "unpolarized"|"s"|"p" or an angle psi in degr…”
    • methodstring
    • optionsobject or null“time_limit (s, default 300), max_iterations, min_thickness (nm; guaranteed in the result: thin layers are clamped or removed and the design re-refined with tha…”
    • wait_secondsnumber
  • “Parameter sweep run in parallel on all cores as a background job.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    5 inputs, 3 required
    • operationstringrequired
    • templateobjectrequired“Arguments of the operation, where any value written "$name" (or "${name}" inside a string) is replaced by the swept parameter `name`.”
    • parametersobjectrequired“e.g.”
    • modestring
    • labelstring
  • run_optimization_campaign

    “Many optimizations from different starting designs, in parallel; ranks distinct results (by yield first when a tolerance stage is requested, then targets met, merit, layer count, total thickness) and…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    8 inputs, 1 required
    • targetsarrayrequired“Targets, each {"kind": "R"|"T"|"A"|"R_phase"|"T_phase"|"R_GD"|"T_GD"|"R_GDD"|"T_GDD", "angle": 0, "polarization": "unpolarized"|"s"|"p" or an angle psi in degr…”
    • startsarray or null“Explicit starting designs.”
    • random_startsobject or null“Generate starts: {"count": 50, "materials": ["TiO2", "SiO2"], "n_layers": [5, 25], "thickness": [20, 200], "substrate": "BK7", "seed": 1, ...other design keys}.”
    • methodsarray
    • optionsobject or null“Same as optimize_design options, applied to every optimization (e.g.”
    • top_ninteger
    • toleranceobject or null“Optional yield stage on the top_n designs: {"n_trials": 200, "thickness_error": {"type": "relative", "sigma": 0.01}, "index_error": {"sigma": 0.005}, "seed": 0}”
    • labelstring
  • tolerance_analysis

    “Monte Carlo yield: random thickness (and optional index) errors; a trial passes when every target is met.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    7 inputs, 2 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • targetsarrayrequired“Targets, each {"kind": "R"|"T"|"A"|"R_phase"|"T_phase"|"R_GD"|"T_GD"|"R_GDD"|"T_GDD", "angle": 0, "polarization": "unpolarized"|"s"|"p" or an angle psi in degr…”
    • n_trialsinteger
    • thickness_errorobject or null“{"type": "relative"|"absolute", "sigma": 0.01 (fraction) or nm, "distribution": "normal"|"uniform", "systematic": 0.0 (common relative offset)}”
    • index_errorobject or null“{"sigma": 0.005} relative index error, drawn per material per trial”
    • seedinteger
    • wait_secondsnumber
  • simulate_random_errors

    “OpenFilters' Preproduction > Simulate random errors: the spread of R, T, A, phase, GD, GDD (and colour) curves when every layer thickness is off by a random error, without targets (tolerance_analysis…”

    Publisher declares: read-only yes · open-world no

    15 inputs, 1 required
    • designobjectrequired“Design: {"substrate": "BK7", "incident_medium": "void", "center_wavelength": 550, "substrate_thickness_mm": 1, "layers": [{"material": "TiO2", "thickness": 58.…”
    • quantitiesarray
    • wavelengthsobject or array or null“{"from": 380, "to": 1100, "step": 1} or an explicit list of wavelengths (nm).”
    • anglenumber
    • polarizationstring or number“"s", "p", "unpolarized", or a polarization angle psi in degrees from 0 to 90 (as in the OpenFilters dialogs: R = sin^2(psi) Rs + cos^2(psi) Rp; 0 = p, 90 = s, …”
    • thickness_errorobject or null“{"type": "relative" (value a fraction, 0.01 = 1 %) | "absolute" (value in nm), "value": 0.01 ("sigma" is accepted too), "distribution": "uniform" (within +/- v…”
    • nb_testsinteger
    • illuminantstring
    • observerstring
    • showobject or null“What the plots draw, as the dialog's Show boxes: {"all_results": false, "mean": false, "std_devs": null (e.g.”
    • targetsarray or null
    • seedinteger
    • sample_pointsinteger
    • save_all_resultsboolean
    • plotboolean
  • “Progress of a background job (tasks done/total, failures, ETA, output files when done).”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • job_idstringrequired
  • “Most recent background jobs, newest first.”

    Publisher declares: read-only yes · open-world no

    1 input
    • limitinteger
  • “Result rows of a job (campaigns are ranked best first; batches in task order unless sort_by is given).”

    Publisher declares: read-only yes · open-world no

    6 inputs, 1 required
    • job_idstringrequired
    • top_ninteger
    • sort_bystring or null
    • descendingboolean
    • include_designsboolean
    • plotboolean
  • “Cancel the pending tasks of a running background job.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • job_idstringrequired
  • load_projecton 3 other servers

    “Read an OpenFilters .ofp project: returns its designs (as design JSON) and targets.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • pathstringrequired
    • full_graded_arraysboolean
  • “Write designs and their targets to an .ofp project that opens in the OpenFilters GUI.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    4 inputs, 2 required
    • pathstringrequired
    • designsarrayrequired
    • targetsarray or null
    • commentstring

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-20; remote servers are read the day they appear and again about every 30 days; package servers at the monthly refresh.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
32% of 141
Tools with a description
100% of 28
Typical description length
477 characters

The tool set

Counted from the listing

Tools
28
Size of the list
about 16,582 tokens for an agent to load (characters ÷ 4)
Naming
28 of 28 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 28 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the PyPI package mcp-for-openfilters

Our sandbox started this package on 2026-11-20 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "mcp-for-openfilters": {
      "command": "uvx",
      "args": [
        "mcp-for-openfilters==0.2.2"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "mcp-for-openfilters": {
      "command": "uvx",
      "args": [
        "mcp-for-openfilters==0.2.2"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "mcp-for-openfilters": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-for-openfilters==0.2.2"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"mcp-for-openfilters","type":"stdio","command":"uvx","args":["mcp-for-openfilters==0.2.2"]}'
Claude Code
claude mcp add --transport stdio mcp-for-openfilters -- uvx mcp-for-openfilters==0.2.2
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "mcp-for-openfilters": {
      "command": "uvx",
      "args": [
        "mcp-for-openfilters==0.2.2"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "mcp-for-openfilters": {
      "command": "uvx",
      "args": [
        "mcp-for-openfilters==0.2.2"
      ]
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.mcp-for-openfilters]
command = "uvx"
args = ["mcp-for-openfilters==0.2.2"]
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "mcp-for-openfilters": {
      "command": "uvx",
      "args": [
        "mcp-for-openfilters==0.2.2"
      ]
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- uvx mcp-for-openfilters==0.2.2
  • This runs the publisher's code on your machine (uvx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.2.2
Latest stable
0.2.2
Status
current
Withdrawn
no

Source: pypi.org · 2026-11-19; new versions read the day they appear; the rest re-read about every 30 days. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-11-07 (OSV.dev; each bar counts advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha256-2a2ec49ecc5ceb18e…
License
GPL-2.0-or-later

Source: the package registry · 2026-11-19.

Usage

Downloads
1,347 in the last month

Source: pypistats.org · 2026-11-19.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Published package can be startedStarted and answeredmatchesour test · 2026-11-20
Version 0.2.2 on PyPIExists and can be installedmatchesPyPI · 2026-11-19
Repository github.com/BBrunoEsteves/mcp-for-openfiltersOpens publiclymatchesapi.github.com · 2026-11-19

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.BBrunoEsteves
GitHub owner
a personal account (BBrunoEsteves)
Repository
github.com/BBrunoEsteves/mcp-for-openfilters
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-07; read when the server is listed, then about every 30 days; an operator can ask for an earlier re-read.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

7 of 8 record checks met · 1 does not apply

  • #2,679 of 20,725 packages by monthly downloads, tied with 4 others
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • MetPackage names its licence with a standard (SPDX) identifierGPL-2.0-or-later
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-07). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.BBrunoEsteves/mcp-for-openfilters

Answered from the data above

Who publishes io.github.BBrunoEsteves/mcp-for-openfilters?

The registry ties the namespace io.github.BBrunoEsteves to the GitHub account BBrunoEsteves; only its owner can publish under it. Its linked repository, github.com/BBrunoEsteves/mcp-for-openfilters, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.BBrunoEsteves/mcp-for-openfilters safe to install?

We do not rate servers as safe or unsafe. 7 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.BBrunoEsteves/mcp-for-openfilters been security tested?

Partly. 4 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. ProtocolProbe publishes no security verdict for a named server.

Does io.github.BBrunoEsteves/mcp-for-openfilters publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 0.2.2, the latest stable release on PyPI.

Where is the source code of io.github.BBrunoEsteves/mcp-for-openfilters?

In github.com/BBrunoEsteves/mcp-for-openfilters, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-20
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not applicable
  17. Consent handling: not applicable
  18. Sign-in metadata: not applicable

4 exercised9 not run (reason given)5 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
Not run, with the reason · 9
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
Does not apply to this server · 5
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-11-20, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted the published package in an isolated sandbox (read-only mode)
  2. 11,146 msConnected after 0 redirects.
  3. Read the inventory: 28 tools, 9 resources, 5 prompts.
  4. 13,148 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why. How often each is read again: methodology.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-07; not classified yet
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
api.github.com · 2026-11-07 · read when a version is new, and at the monthly refresh
Hosting type
registry · 2026-11-07 · read from the registry entry; changes when a new version is listed
MCP capability
prompts, resources, tools
our test · 2026-11-20
Transport
standard input/output
registry · 2026-11-07 · read from the registry entry; changes when a new version is listed
Required credentials
none declared
registry · 2026-11-07 · no declaration is not a guarantee · read from the registry entry; changes when a new version is listed
Package registry
registry · 2026-11-07 · read from the registry entry; changes when a new version is listed
Freshness
0–30 days
registry updatedAt · 2026-11-07
Lifecycle status
registry · 2026-11-07 · status read from the registry every day
License class
package registry · 2026-11-19 · new versions read the day they appear; the rest re-read about every 30 days
Integrity hash
declared (sha256)
package registry · 2026-11-19 · new versions read the day they appear; the rest re-read about every 30 days
Signature / provenance
does not apply
PyPI publishes no registry signature or attestation equivalent to npm dist.signatures
Dependency advisories
none known
OSV.dev · 2026-11-07 · read when a version is new, and at the monthly refresh
Popularity
1,347 downloads a month
package registry · 2026-11-19 · new versions read the day they appear; the rest re-read about every 30 days
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-19 · new versions read the day they appear; the rest re-read about every 30 days
Maintenance
api.github.com · 2026-11-19 · new versions read the day they appear; the rest re-read about every 30 days
Environment
your machine
where it runs, from the hosting type · 2026-11-07 · read from the registry entry; changes when a new version is listed

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.BBrunoEsteves/mcp-for-openfilters: MCP server record.” Data checked 2026-11-20. https://protocolprobe.com/mcp/servers/io.github.BBrunoEsteves/mcp-for-openfilters

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 7 of 8 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.BBrunoEsteves/mcp-for-openfilters)](https://protocolprobe.com/mcp/servers/io.github.BBrunoEsteves/mcp-for-openfilters)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology