FillStub - options trading journal
REMOTE · MCP.FILLSTUB.COM · SCANNED SEP 30
Options journal from broker exports: contract lifecycle, Section 1256 vs 8949 tax split, intervals
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 130 tokens (~130/item across 0 items; 0 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
- Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the FillStub - options trading journal MCP server?
FillStub - options trading journal is a hosted endpoint at https://mcp.fillstub.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.fillstub.com
claude mcp add --transport http com-fillstub-options-trading-journal 'https://mcp.fillstub.com/mcp'
{
"mcpServers": {
"com-fillstub-options-trading-journal": {
"url": "https://mcp.fillstub.com/mcp"
}
}
} {
"servers": {
"com-fillstub-options-trading-journal": {
"type": "http",
"url": "https://mcp.fillstub.com/mcp"
}
}
} [mcp_servers.com-fillstub-options-trading-journal] url = "https://mcp.fillstub.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-fillstub-options-trading-journal": {
"type": "remote",
"url": "https://mcp.fillstub.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-fillstub-options-trading-journal --url 'https://mcp.fillstub.com/mcp' --transport streamable-http
mcp_servers:
com-fillstub-options-trading-journal:
url: "https://mcp.fillstub.com/mcp" {
"McpServers": {
"com-fillstub-options-trading-journal": {
"Transport": "http",
"Url": "https://mcp.fillstub.com/mcp"
}
}
} assistant mcp add com-fillstub-options-trading-journal -t streamable-http -u 'https://mcp.fillstub.com/mcp'
{
"mcpServers": {
"com-fillstub-options-trading-journal": {
"type": "http",
"url": "https://mcp.fillstub.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 30 Sept 2026 · Probed https://mcp.fillstub.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fillstub.com | CN=WE1,O=Google Trust Services,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8fb33ec88faaa5160eb2238b3cc94a11 |
| SANs: fillstub.com, mcp.fillstub.com, *.mcp.fillstub.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.fillstub.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fillstub.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.fillstub.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.fillstub.com/mcp | Inconclusive | 405 |
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 →
No tool schema has been captured from this endpoint yet.
What is the FillStub - options trading journal MCP server?
FillStub - options trading journal is an MCP server listed in the public MCP registry as com.fillstub/options-trading-journal. Options journal from broker exports: contract lifecycle, Section 1256 vs 8949 tax split, intervals. This page covers its hosted endpoint (https://mcp.fillstub.com/mcp).
Is the FillStub - options trading journal MCP server safe to use?
FillStub - options trading journal scores 61 out of 100 on VerifyMCP. 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.
Does the FillStub - options trading journal MCP server require authentication?
No. We connected to FillStub - options trading journal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FillStub - options trading journal MCP server still maintained?
FillStub - options trading journal is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.