io.github.sbrunner-atx/n3fjp-mcp
PYPI · N3FJP-MCP · SCANNED SEP 21
Log amateur-radio QSOs to N3FJP logging software over its TCP API.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1628 tokens (~162/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.sbrunner-atx/n3fjp-mcp server?
io.github.sbrunner-atx/n3fjp-mcp runs locally as a PyPI package, launched with uvx n3fjp-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · n3fjp-mcp
claude mcp add sbrunner-atx-n3fjp-mcp -- uvx n3fjp-mcp
{
"mcpServers": {
"sbrunner-atx-n3fjp-mcp": {
"command": "uvx",
"args": [
"n3fjp-mcp"
]
}
}
} {
"servers": {
"sbrunner-atx-n3fjp-mcp": {
"command": "uvx",
"args": [
"n3fjp-mcp"
]
}
}
} codex mcp add sbrunner-atx-n3fjp-mcp -- uvx n3fjp-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sbrunner-atx-n3fjp-mcp": {
"type": "local",
"command": [
"uvx",
"n3fjp-mcp"
],
"enabled": true
}
}
} openclaw mcp add sbrunner-atx-n3fjp-mcp --command uvx --arg n3fjp-mcp
mcp_servers:
sbrunner-atx-n3fjp-mcp:
command: "uvx"
args: ["n3fjp-mcp"] {
"McpServers": {
"sbrunner-atx-n3fjp-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"n3fjp-mcp"
]
}
}
} assistant mcp add sbrunner-atx-n3fjp-mcp -t stdio -c uvx -a n3fjp-mcp
{
"mcpServers": {
"sbrunner-atx-n3fjp-mcp": {
"command": "uvx",
"args": [
"n3fjp-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −12
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.27 ▲ functional
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 9 Sept 26 +12
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- Package version: 0.3.0 → 0.3.1 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed pypi/n3fjp-mcp@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bandmode ~191
Change band, mode, and frequency before logging. operations: - change_freq (value=Hz): set the frequency (and thus band) via the rig interface. Use suppress_mode_default=true to keep the current mode rather than letting CW/phone segments flip it. - set_band (value=band, e.g. "20"): write the band box (rig interface OFF only). - set_mode (value=mode, e.g. "DIG"): write the mode box (rig interface OFF only). - ignore_rig_polls (value=bool): pause rig polling so band/mode boxes can be written while a rig is connected. Remember to set it back to false. Always make sure the program is on the correct band and mode before ENTER.
| Name | Type | Req | Description |
|---|---|---|---|
| operation | string | yes | – |
| suppress_mode_default | boolean | – | – |
| value | – | – | – |
No output schema declared.
No examples provided.
database ~286
Direct database operations on individual records. These are ordinary writes (the *Needs Approval* tier — same as logging), so they can be globally allowed in the client for automation. The ONLY hard block is a whole-database wipe/overwrite, gated by N3FJP_ALLOW_DB_WIPE. operations: - add_direct (fields={fldCall:..., fldBand:...}, exclude_dupes): insert a record directly, bypassing N3FJP's scoring. Prefer log's log_qso/ENTER. - delete (where="fldPrimaryID=123"): delete matching records. A missing or empty WHERE would clear the whole table and is refused unless N3FJP_ALLOW_DB_WIPE is on. - sql (sql="..."): run a raw SQL statement against the Access database. Only statements that could wipe/overwrite the whole database (DROP, TRUNCATE, unscoped DELETE/UPDATE) are refused unless N3FJP_ALLOW_DB_WIPE is on; scoped statements run normally. - checklog / openlog: ask N3FJP to reload new / all records. - sqlclose: close the SQL connection.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_dupes | boolean | – | – |
| fields | – | – | – |
| operation | string | yes | – |
| sql | – | – | – |
| where | – | – | – |
No output schema declared.
No examples provided.
diagnostics ~79
Host + network diagnostics for troubleshooting connectivity. Does NOT connect to N3FJP. Reports the resolved N3FJP_HOST/PORT, this process's Python and hostname, and the host's network interfaces — so you can tell whether the process can even see the target's network (e.g. when running host-side vs. sandboxed).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fields ~142
Read entry-box (text field) values. operations: - read (field=name): read one box. `field` may be a friendly name (call, rst_rcvd, class, section, name, …) or a raw control id (TXTENTRY…). - visible: every field the current contest shows, with values. - all: every field (regardless of visibility), with values. Derived fields (country_worked, cq_zone, itu_zone, continent, prefix) are readable here but are computed by N3FJP from the call — never write them.
| Name | Type | Req | Description |
|---|---|---|---|
| field | – | – | – |
| operation | string | yes | – |
No output schema declared.
No examples provided.
log ~339
Logbook entry: set fields, run Call-tab, and ENTER a QSO. The headline tool. operations: - log_qso: the automatic-logging flow. Provide `call` (and usually `exchange`, a dict of friendly field names → values, e.g. {"class": "2A", "section": "CT"}). Sets the call, runs CALLTAB (dupe check + lookups) unless calltab=false, sets the exchange, then ENTER. Returns the number of records added and any dupe response. - set (field, value): write one entry box. - set_many (fields={...}): write several entry boxes. - calltab: run CALLTAB (after setting the call). - enter: log the current form. Returns records_added plus a `logged` boolean derived from the QSO-count delta / ENTEREVENT — trust `logged`, not records_added, which can report 0 on success in networked mode. Do not retry when logged=true (creates duplicates). - clear: clear the entry form. - focus (field): move focus to a box (e.g. to auto-fill default RST). Tip: `contest` (e.g. "field_day", "cq_wpx") lets the tool warn if the exchange is missing a field that contest needs.
| Name | Type | Req | Description |
|---|---|---|---|
| call | – | – | – |
| calltab | boolean | – | – |
| contest | – | – | – |
| exchange | – | – | – |
| field | – | – | – |
| fields | – | – | – |
| operation | string | yes | – |
| value | – | – | – |
No output schema declared.
No examples provided.
n3fjp_call ~160
Escape hatch: send any raw N3FJP command and return the parsed reply. `command` may be a bare command id ("PROGRAM"), a full envelope ("<CMD><PROGRAM></CMD>"), or the inner form ("<PROGRAM>") — it is normalised and CRLF-terminated for you. `expect` is the response id to wait for. This reaches anything not surfaced by a group tool, including newer commands. Like the group tools, it runs at the *Needs Approval* tier; the only hard block is a raw SQL statement that could wipe/overwrite the whole database, which still requires the N3FJP_ALLOW_DB_WIPE switch.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | – |
| expect | – | – | – |
No output schema declared.
No examples provided.
notifications ~96
Opt-in push events from N3FJP (field updates, enter/calltab, dupes). operations: - enable: turn on all-field-update notifications. - disable: turn them off. - drain: return and clear the buffered notification blocks received so far. MCP is request/response, so events are buffered and you pull them with drain rather than receiving a live stream.
| Name | Type | Req | Description |
|---|---|---|---|
| operation | string | yes | – |
No output schema declared.
No examples provided.
query ~62
Read-only program queries. operations: program (name/version/API version), qso_count, next_serial, log_path, settings_path, shared_path, qso_rate (contest stats), band_mode_freq (current band/mode/frequency).
| Name | Type | Req | Description |
|---|---|---|---|
| operation | string | yes | – |
No output schema declared.
No examples provided.
search ~222
Search and list the log (read-only). operations: - list (count, include_all): the most recent QSOs (primary fields, or every field with include_all=true). - search (call/band/mode/dxcc/country/confirmed, include_all, max_records): find matching QSOs. Prefer dxcc (ADIF number) over country (must match N3FJP's spelling exactly). mode is normalized to CW/PH/DIG. - dupecheck (call): is this call a dupe? Returns previous-contact detail or empty if new. (No side effects, unlike the log tool's calltab.) - entity (call, band, mode): all-time-new/worked/confirmed status.
| Name | Type | Req | Description |
|---|---|---|---|
| band | – | – | – |
| call | – | – | – |
| confirmed | – | – | – |
| count | – | – | – |
| country | – | – | – |
| dxcc | – | – | – |
| include_all | boolean | – | – |
| max_records | – | – | – |
| mode | – | – | – |
| operation | string | yes | – |
No output schema declared.
No examples provided.
status ~51
Snapshot: program, version, API version, QSO count, band/mode/frequency, log path. A quick health check that also confirms the connection and which N3FJP program/contest is loaded.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.sbrunner-atx/n3fjp-mcp server?
io.github.sbrunner-atx/n3fjp-mcp is listed in the public MCP registry as io.github.sbrunner-atx/n3fjp-mcp. Log amateur-radio QSOs to N3FJP logging software over its TCP API. This page covers its PyPI package (n3fjp-mcp).
Is the io.github.sbrunner-atx/n3fjp-mcp server safe to use?
io.github.sbrunner-atx/n3fjp-mcp scores 56 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.sbrunner-atx/n3fjp-mcp server expose?
io.github.sbrunner-atx/n3fjp-mcp exposes 10 tools: status, diagnostics, query, fields, log, and 5 more. Their descriptions and schemas cost roughly 1,628 tokens of context every time the server is loaded.
Is the io.github.sbrunner-atx/n3fjp-mcp server still maintained?
io.github.sbrunner-atx/n3fjp-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.sbrunner-atx/n3fjp-mcp server under?
io.github.sbrunner-atx/n3fjp-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.