io.github.Toinedotcom/toolforte
REMOTE · TOOLFORTE.COM · 2 COMPONENTS
Exact IBAN, VAT, cron, regex answers; HTML/URL to hosted PDF or screenshot; agent memory; workflows.
Available components
Last scanned (20 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Developer Tools
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3052 tokens (~190/item across 16 items; 14 tools + 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 13 Nov 26 0
- New resource “ownership” functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 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
- 30 Oct 26 +56
- Transport: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- The server rewrote its instructions, which are the text every model session reads security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 23 Oct 26 38
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 22 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “workflow_list” rewrote its description, which is the text the model reads security
- Tool “workflow_run” rewrote its description, which is the text the model reads security
- Tool “working_days_between” rewrote its description, which is the text the model reads security
- Tool “test_regex” rewrote its description, which is the text the model reads security
- Tool “search_tools” rewrote its description, which is the text the model reads security
- Tool “format_json” rewrote its description, which is the text the model reads security
- Tool “dutch_public_holidays” rewrote its description, which is the text the model reads security
- Tool “csv_to_json” rewrote its description, which is the text the model reads security
- Tool “calculate_vat” rewrote its description, which is the text the model reads security
- Tool “text_diff” rewrote its description, which is the text the model reads security
- Tool “validate_iban” rewrote its description, which is the text the model reads security
- Tool “workflow_propose” rewrote its description, which is the text the model reads security
- Schema quality: 161 → 199 ▼ functional
- Server version: 1.11.0 → 1.12.0 functional
- 14 Oct 26 0
- Stability: fail → pass ▲ security
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 Nov 2026 · Probed https://toolforte.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=toolforte.com | CN=YR2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | RSA 2048 | SHA256-RSA | 59b675ce46308a91b031f58a68449bdcd91 |
| SANs: toolforte.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of toolforte.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| toolforte.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://toolforte.com/.well-known/oauth-protected-resource/api/mcp"
Bearer resource_metadata="https://toolforte.com/.well-known/oauth-protected-resource/api/mcp" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: https: blob:; media-src 'self' blob:; font-src 'self' data: blob: https://fonts.gstatic.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://pagead2.googlesyndication.com https://tpc.googlesyndication.com https://*.adtrafficquality.google https://www.googletagmanager.com https://fundingchoicesmessages.google.com https://www.google.com https://va.vercel-scripts.com https://cdn.jsdelivr.net; worker-src 'self' blob:; connect-src 'self' blob: https://*.supabase.co https://pagead2.googlesyndication.com https://tpc.googlesyndication.com https://*.adtrafficquality.google https://www.googletagmanager.com https://fundingchoicesmessages.google.com https://www.google.com https://googleads.g.doubleclick.net https://www.google-analytics.com https://*.google-analytics.com https://va.vercel-scripts.com h |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://toolforte.com/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://toolforte.com/api/mcp |
| Authorisation server | https://ecoeuuzxkffywfsktcud.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://toolforte.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://toolforte.com/api/mcp | HTTPS enforced | 308 | https://toolforte.com/api/mcp |
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 →
calculate_vat VAT Calculator ~143
Use this when you need to add VAT to a net amount or take it out of a gross amount. Example prompt: "What is 21% BTW on 1,250 euros?" Add VAT to a net amount or extract VAT from a gross amount at any rate (e.g. 21 for Dutch BTW). Returns exact net, VAT, and gross amounts rounded to cents. Costs 1 credit. The answer is deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | The amount |
| mode | string | yes | add = amount is net, add VAT on top; extract = amount is gross, split out VAT |
| rate | number | yes | VAT rate in percent |
| Name | Type | Req | Description |
|---|---|---|---|
| gross | number | – | – |
| net | number | – | – |
| rate | number | – | – |
| result | – | – | The result, when it is not an object |
| vat | number | – | – |
No examples provided.
csv_to_json CSV to JSON ~94
Use this when you need CSV data as JSON objects. Example prompt: "Turn this CSV export into JSON." Parse CSV data into JSON with delimiter auto-detection and quoted-field handling. Costs 1 credit. The answer is deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| csv | string | yes | The CSV text; the delimiter is detected automatically |
| firstRowHeaders | boolean | – | Treat the first row as column names and return objects (default true) |
| Name | Type | Req | Description |
|---|---|---|---|
| delimiter | string | – | – |
| json | array | – | – |
| result | – | – | The result, when it is not an object |
| row_count | number | – | – |
No examples provided.
describe_tool Describe a ToolForte tool ~70
The full definition of one ToolForte tool by name: description, argument schema (JSON Schema), output schema, annotations, cost and an example call. Use it after search_tools when the argument summary is not enough. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The tool name, for example validate_iban |
| Name | Type | Req | Description |
|---|---|---|---|
| annotations | object | – | – |
| credits | number | – | – |
| description | string | – | – |
| example | object | – | – |
| inputSchema | object | – | – |
| listed | boolean | – | – |
| name | string | – | – |
| outputSchema | object | – | – |
| result | – | – | The result, when it is not an object |
| title | string | – | Page title |
No examples provided.
dutch_public_holidays Dutch Public Holidays ~109
Use this when you need the dates of the Dutch public holidays in a given year. Example prompt: "When is Ascension Day in the Netherlands in 2027?" Exact Dutch public holidays for a year, including movable feasts (Easter, Ascension, Whitsun) and King's Day rules. Use this instead of computing Dutch holidays yourself. Costs 1 credit. The answer is deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | yes | Calendar year, 1900 to 2200 |
| Name | Type | Req | Description |
|---|---|---|---|
| holidays | array | – | – |
| result | – | – | The result, when it is not an object |
| year | number | – | – |
No examples provided.
format_json JSON Formatter ~100
Use this when you need to check whether JSON is valid or make it readable. Example prompt: "Why does this JSON fail to parse?" Validate and pretty-print JSON with a real parser. Returns formatted JSON or the exact parse error. Costs 1 credit. The answer is deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| indent | integer | – | Spaces per indentation level, 0 to 8 (default 2) |
| json | string | yes | The JSON text to validate and format |
| Name | Type | Req | Description |
|---|---|---|---|
| output | string | – | The final output of the workflow |
| result | – | – | The result, when it is not an object |
| valid | boolean | – | Whether the input passed every check |
No examples provided.
run_tool Run any ToolForte tool by name ~99
Run any ToolForte tool by name with its arguments, whether or not it is listed in this session. The result, the cost and the metering are exactly what the tool gives when called directly; run_tool itself is free. Find names with search_tools and schemas with describe_tool.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | The tool's arguments, as describe_tool documents them |
| name | string | yes | The tool name, for example calculate_vat |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The result, when it is not an object |
No examples provided.
search_tools Find a ToolForte tool ~190
Use this when you need a ToolForte tool that is not in the current tool list. Example prompt: "Is there a tool that converts YAML to JSON?" Find ToolForte tools by what you want done, for example "iban", "vat", "pdf merge", "working days", "csv to json", "screenshot". ToolForte has over a hundred exact tools (validation, conversion, Dutch tax and dates, test data, files, AI); a session lists a small core of them and this is how you reach the rest. Returns the best matches with their arguments and cost. Then call the tool by name, or through run_tool. Free. The answer is deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many matches to return, 1 to 50 (default 8) |
| query | string | – | Words describing the job. Empty lists every tool the server has. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of items |
| note | string | – | – |
| query | string | – | – |
| result | – | – | The result, when it is not an object |
| tools | array | – | – |
| total | number | – | – |
No examples provided.
test_regex Regex Tester ~126
Use this when you need to know what a regular expression actually matches. Example prompt: "Does this regex match every email address in this text?" Run a JavaScript regular expression against a test string using a real regex engine. Returns all matches with capture groups and indices. Costs 1 credit. The answer is deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| flags | string | – | Regex flags such as g, i, m, s, u (default g) |
| pattern | string | yes | JavaScript regular expression source, without the slashes |
| text | string | yes | The text to run the expression against |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of items |
| matches | array | – | – |
| result | – | – | The result, when it is not an object |
No examples provided.
text_diff Text Diff ~92
Use this when you need to see exactly which lines changed between two versions of a text. Example prompt: "What changed between these two versions of the contract clause?" Compute an exact line-based diff between two texts with add/remove/unchanged stats. Costs 1 credit. The answer is deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| modified | string | yes | The text after the change |
| original | string | yes | The text before the change |
| Name | Type | Req | Description |
|---|---|---|---|
| lines | array | – | – |
| result | – | – | The result, when it is not an object |
| stats | object | – | – |
No examples provided.
validate_iban IBAN Validator ~390
Use this when you need to know whether an IBAN is well formed before using it. Example prompt: "Is NL91ABNA0417164300 a valid IBAN?" Check whether an IBAN is well formed: the mod-97 checksum, the country code, the length that country's IBAN must have, and whether every position holds the kind of character that country allows there (mod-97 turns letters into numbers, so on its own it cannot see a capital O typed in place of a zero). Returns validity, country, and where known the bank identifier printed inside the IBAN. This is a format check, not a bank check: a passing IBAN can still name a bank code that never existed or has since merged away, and says nothing about whether the account exists or can receive a payment. For twelve countries it also verifies the national check digit that the bank computes over the bank code and account number (BE, FR, MC, ES, IT, SM, PT, SI, PL, TN, EE, HU); nationalCheck 'failed' there means the number is very probably invented, since that digit cannot be back-computed the way the mod-97 pair can. Absent nationalCheck means not checked, never approved. For Dutch IBANs it also names the institution behind the four-letter bank code, including codes that no longer issue accounts; an unrecognised code does not make the IBAN invalid. A territory that borrows another country's IBAN (Reunion, Guernsey, Aland and the like) is reported with the prefix it actually uses, since no IBAN starts with RE or GG. Never guess whether an IBAN is well formed: use this tool. Do not present a pass as confirmation that money can be sent. Costs 1 credit. The answer is deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| iban | string | yes | The IBAN to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| accountNumber | string | – | – |
| bankCode | string | – | – |
| checkDigits | string | – | – |
| country | string | – | – |
| countryName | string | – | – |
| iban | string | – | – |
| institution | object | – | – |
| result | – | – | The result, when it is not an object |
| valid | boolean | – | Whether the input passed every check |
No examples provided.
workflow_list List saved workflows ~189
List the workflows saved to the ToolForte account this API key belongs to. A workflow runs several ToolForte tools in order, passing each one the output of an earlier step, so it does a whole job in one call instead of you orchestrating the steps yourself. Returns each workflow's id, the inputs it expects, the steps it runs and what a run costs. Call this first: workflow_run needs an id from here. Requires an API key, because a workflow belongs to an account. Get a key in one request with POST https://toolforte.com/api/v1/keys/bootstrap and {"email":"you@example.com"}, which emails it to that address, or create one at https://toolforte.com/developers, and send it on the MCP connection as the header Authorization: Bearer tf_...
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return, newest first. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of items |
| result | – | – | The result, when it is not an object |
| workflows | array | – | The workflows on the account |
No examples provided.
workflow_propose Propose a workflow for a goal ~279
Describe a job in plain words and get back a workflow built only from tools this server really has: a name, the inputs it needs, and the steps in order, each with one sentence on why it is there. The proposal is honest about gaps: partial is true and missing names what could not be done, and when nothing here fits the answer says so instead of inventing a step. Send save: true to keep it on the account, after which workflow_run can run it by the returned id. Costs 10 credits, the price of one AI generation, charged once per proposal. Requires an API key linked to a ToolForte account. Get a key in one request with POST https://toolforte.com/api/v1/keys/bootstrap and {"email":"you@example.com"}, which emails it to that address, or create one at https://toolforte.com/developers, and send it on the MCP connection as the header Authorization: Bearer tf_...
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | The job to be done, in a sentence or two, for example: take a CSV of invoices, sum the amounts per customer and write the totals to a spreadsheet. |
| save | boolean | – | Save the proposed workflow to the account so workflow_run can run it. Default false: the proposal is returned for you to read first. |
| Name | Type | Req | Description |
|---|---|---|---|
| creditsCharged | number | – | Credits spent by this call |
| definition | object | – | The proposed workflow: name, declared inputs and steps |
| explanation | string | – | Plain words on what the workflow does and why each step is there |
| missing | array | – | What could not be done, named |
| partial | boolean | – | Whether the workflow only does part of what was asked |
| result | – | – | The result, when it is not an object |
| saved | object | – | The saved workflow's id and name, when save was true |
| steps | array | – | What each step produced |
No examples provided.
workflow_run Run a saved workflow ~262
Run one saved workflow by id and return what every step produced. Get the id and the input keys from workflow_list. Each step costs the credits its own tool costs, normally 1 per step, and the credit for this call counts as the first step's rather than being charged on top. Steps run in order and stop at the first failure; the result says which step stopped it and what was spent up to that point. Check the "substitutions" field when it is present: it lists values a step supplied that the tool replaced with its own, which means the run succeeded on a value you did not send. Requires an API key, because a workflow belongs to an account. Get a key in one request with POST https://toolforte.com/api/v1/keys/bootstrap and {"email":"you@example.com"}, which emails it to that address, or create one at https://toolforte.com/developers, and send it on the MCP connection as the header Authorization: Bearer tf_...
| Name | Type | Req | Description |
|---|---|---|---|
| inputs | object | – | Values for the workflow's declared inputs, keyed by the input key that workflow_list reports. Omit for a workflow that declares none. |
| workflowId | string | yes | The id of a workflow from workflow_list. |
| Name | Type | Req | Description |
|---|---|---|---|
| creditsCharged | number | – | Credits spent by this call |
| durationMs | number | – | – |
| name | string | – | – |
| ok | boolean | – | Whether the run completed |
| output | object | – | The final output of the workflow |
| result | – | – | The result, when it is not an object |
| runId | string | – | – |
| steps | array | – | What each step produced |
| stepsDefined | number | – | – |
| stepsRun | number | – | – |
| workflowId | string | – | – |
No examples provided.
working_days_between Working Days Calculator ~128
Use this when you need the number of working days between two dates. Example prompt: "How many working days are there between 1 March and 30 April 2027?" Count working days (Mon-Fri) between two dates inclusive, optionally excluding Dutch public holidays. Exact date math for SLA, payroll, and planning questions. Costs 1 credit. The answer is deterministic.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | YYYY-MM-DD |
| excludeDutchHolidays | boolean | – | Skip Dutch public holidays that fall on a weekday (default true) |
| start | string | yes | YYYY-MM-DD |
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | – |
| holidaysExcluded | array | – | – |
| result | – | – | The result, when it is not an object |
| start | string | – | – |
| totalDays | number | – | – |
| weekendDays | number | – | – |
| workingDays | number | – | – |
No examples provided.
How do I install the io.github.Toinedotcom/toolforte MCP server?
io.github.Toinedotcom/toolforte is a hosted endpoint at https://toolforte.com/api/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 · toolforte.com
claude mcp add --transport http toinedotcom-toolforte 'https://toolforte.com/api/mcp'
What is the io.github.Toinedotcom/toolforte MCP server?
io.github.Toinedotcom/toolforte is an MCP server listed in the public MCP registry as io.github.Toinedotcom/toolforte. Exact IBAN, VAT, cron, regex answers; HTML/URL to hosted PDF or screenshot; agent memory; workflows. This page covers its hosted endpoint (https://toolforte.com/api/mcp).
Is the io.github.Toinedotcom/toolforte MCP server safe to use?
io.github.Toinedotcom/toolforte scores 94 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.
What tools does the io.github.Toinedotcom/toolforte MCP server expose?
io.github.Toinedotcom/toolforte exposes 14 tools: text_diff, format_json, csv_to_json, test_regex, validate_iban, and 9 more. Their descriptions and schemas cost roughly 2,271 tokens of context every time the server is loaded.
Does the io.github.Toinedotcom/toolforte MCP server require authentication?
Yes. io.github.Toinedotcom/toolforte asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.Toinedotcom/toolforte MCP server still maintained?
io.github.Toinedotcom/toolforte is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.Toinedotcom/toolforte MCP server?
VerifyMCP ran 13 checks on io.github.Toinedotcom/toolforte, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.