Local MCP capabilities provider for Expo
Nothing to run from here
DNSFilter is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
57
tools declared
—
trust score
local
runs on your machine
—
calls last 7d
What it does
MCP server for DNSFilter's DNS security/filtering API.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'DNSFILTER_API_KEY=${DNSFILTER_API_KEY}' --transport stdio dnsfilter-mcp '--' docker run -i --rm -e MCP_TRANSPORT=stdio -e DNSFILTER_API_KEY ghcr.io/wyre-ai/dnsfilter-mcp:v1.0.0
# 2 — ask your agent for something these tools do
# dnsfilter_get_qps, dnsfilter_get_qps_active_agents, dnsfilter_get_qps_active_organizations and 54 more
It needs DNSFILTER_API_KEY: this reads it from your environment, so export it first.
DNSFilter costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WAAll 82 servers
WYRE-AI82 servers
14 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts DNSFilter as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Docker installed and running. Only the required variables are passed into the container. To set an optional one (AUTH_MODE, LOG_LEVEL), add -e NAME before the image name and give it a value in the entry’s env: an unset -e would clear the default the image sets. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads DNSFILTER_API_KEY (DNSFilter API key, generated in the DNSFilter dashboard under Account Settings -> Security -> API Keys. Sent as the raw Authorization header value) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx DNSFILTER_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'DNSFILTER_API_KEY=${DNSFILTER_API_KEY}' --transport stdio dnsfilter-mcp '--' docker run -i --rm -e MCP_TRANSPORT=stdio -e DNSFILTER_API_KEY ghcr.io/wyre-ai/dnsfilter-mcp:v1.0.0Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own image: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: DNSFILTER_API_KEY — DNSFilter API key, generated in the DNSFilter dashboard under Account Settings -> Security -> API Keys. Sent as the raw Authorization header value.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
57 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Queries-per-second time series - the closest thing to a live traffic pulse.
No parameter schema on file.
Queries-per-second broken out by active client/agent.
No parameter schema on file.
Queries-per-second broken out by active organization.
No parameter schema on file.
Raw DNS query log entries - domain queried, requester, category, and allow/block result. The most granular, PII-bearing report this connector exposes.
No parameter schema on file.
Clients/agents generating the most traffic.
No parameter schema on file.
Application categories generating the most traffic.
No parameter schema on file.
Content categories generating the most traffic.
No parameter schema on file.
Collections (roaming-client groupings) generating the most traffic.
No parameter schema on file.
Domains queried most often.
No parameter schema on file.
Networks generating the most traffic.
No parameter schema on file.
Organizations generating the most request volume.
No parameter schema on file.
Local users generating the most traffic.
No parameter schema on file.
Application request counts broken out by client/agent.
No parameter schema on file.
Application request counts broken out by collection.
No parameter schema on file.
Application request counts broken out by network.
No parameter schema on file.
Total application request counts.
No parameter schema on file.
Application request counts broken out by local user.
No parameter schema on file.
Total content-category request counts over time.
No parameter schema on file.
Total content-category request counts broken out by organization.
No parameter schema on file.
Content-category request-count summary.
No parameter schema on file.
Client/agent count summary.
No parameter schema on file.
Deployed client/network counts.
No parameter schema on file.
Single-domain request-count summary - use with the domain/fqdn filter.
No parameter schema on file.
Total domain request counts over time.
No parameter schema on file.
Total domain request counts broken out by organization.
No parameter schema on file.
Total domain request counts broken out by local user.
No parameter schema on file.
Total request counts broken out by organization.
No parameter schema on file.
Organization-level request-count summary.
No parameter schema on file.
Total DNS request counts over time.
No parameter schema on file.
Total request counts broken out by client/agent.
No parameter schema on file.
Total request counts broken out by collection.
No parameter schema on file.
Total request counts broken out by geography.
No parameter schema on file.
Total request counts broken out by organization.
No parameter schema on file.
Total request counts broken out by local user.
No parameter schema on file.
Count of roaming (off-network) clients.
No parameter schema on file.
Total blocked-threat counts over time.
No parameter schema on file.
Total blocked-threat counts broken out by organization.
No parameter schema on file.
Total blocked-threat counts broken out by local user.
No parameter schema on file.
List the custom block pages configured for the current user/organization (shown to end users when a request is filtered). Block page IDs from this response are required by dnsfilter_get_block_page.
No parameter schema on file.
Get one custom block page
No parameter schema on file.
List DNSFilter
No parameter schema on file.
Get one content category
No parameter schema on file.
List application categories, used for the application allow/block surface of a policy (distinct from content categories). IDs from this response are required by dnsfilter_get_application_category and can filter traffic-report tools via application_category_ids.
No parameter schema on file.
Get one application category
No parameter schema on file.
Get usage information (plan, term, user/wifi counts, total requests, estimated users) for an organization over a date range. Maximum range is 365 days. Requires an organization ID from dnsfilter_list_organizations.
No parameter schema on file.
Get the detailed (per-metric) breakdown of an organization
No parameter schema on file.
List the networks (sites/locations) visible to this API key, with basic info and whether a filtering policy is assigned. Network IDs from this response are required by dnsfilter_get_network and can scope most traffic-report tools via network_ids.
No parameter schema on file.
Get one network
No parameter schema on file.
Find the network associated with a given source IP address, along with that network\
No parameter schema on file.
Get every visible network
No parameter schema on file.
List the organizations visible to this API key, with basic info (name, type, MSP relationships). Organization IDs from this response are required by dnsfilter_get_organization, dnsfilter_list_networks/policies/block_pages (via organization_id), and every traffic-report tool.
No parameter schema on file.
Get one organization
No parameter schema on file.
Get organization-level settings, optionally scoped to a specific organization or MSP.
No parameter schema on file.
List filtering policies visible to this API key. Policy IDs from this response are required by dnsfilter_get_policy and dnsfilter_get_policy_permissive_mode.
No parameter schema on file.
Get one policy
No parameter schema on file.
Get which policies in an organization allow or block a specific application. Requires an application ID and organization ID.
No parameter schema on file.
Get whether a policy currently has permissive (monitor-only, non-blocking) mode enabled. Requires a policy ID from dnsfilter_list_policies.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public; its licence metadata reads NOASSERTION rather than naming a licence
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install DNSFilter or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is v1.0.0.
v1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish DNSFilter can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.