TinyFn
REMOTE · API.TINYFN.IO · SCANNED SEP 26
500+ deterministic tools for AI agents: math, conversion, validation, hashing, encoding, date/time.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 572 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 20780 tokens (~36/item across 572 items; 572 tools + 0 resources), lean.Pass
- 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 (96% of tools); any adoption earns full credit.Pass
Tool Safety50
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "truncate" implies "truncate" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- Manipulation not yet verified: only 564 of 573 captured unit(s) of tool text has been judged so far, so we will not certify text no model has read as clean.Unverified
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the TinyFn MCP server?
TinyFn is a hosted endpoint at https://api.tinyfn.io/mcp/all/, 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 · api.tinyfn.io
claude mcp add --transport http io-tinyfn-tinyfn 'https://api.tinyfn.io/mcp/all/'
{
"mcpServers": {
"io-tinyfn-tinyfn": {
"url": "https://api.tinyfn.io/mcp/all/"
}
}
} {
"servers": {
"io-tinyfn-tinyfn": {
"type": "http",
"url": "https://api.tinyfn.io/mcp/all/"
}
}
} [mcp_servers.io-tinyfn-tinyfn] url = "https://api.tinyfn.io/mcp/all/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-tinyfn-tinyfn": {
"type": "remote",
"url": "https://api.tinyfn.io/mcp/all/",
"enabled": true
}
}
} openclaw mcp add io-tinyfn-tinyfn --url 'https://api.tinyfn.io/mcp/all/' --transport streamable-http
mcp_servers:
io-tinyfn-tinyfn:
url: "https://api.tinyfn.io/mcp/all/" {
"McpServers": {
"io-tinyfn-tinyfn": {
"Transport": "http",
"Url": "https://api.tinyfn.io/mcp/all/"
}
}
} assistant mcp add io-tinyfn-tinyfn -t streamable-http -u 'https://api.tinyfn.io/mcp/all/'
{
"mcpServers": {
"io-tinyfn-tinyfn": {
"type": "http",
"url": "https://api.tinyfn.io/mcp/all/"
}
}
} 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.
- 25 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
- 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
- 11 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
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 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 Jul 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
- 28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 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 26 Sept 2026 · Probed https://api.tinyfn.io/mcp/all/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.tinyfn.io | CN=YR2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | RSA 2048 | SHA256-RSA | 54eb566768cb74f3218eec54aa7ad821182 |
| SANs: api.tinyfn.io | ||||||
| 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 api.tinyfn.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| tinyfn.io. | 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://api.tinyfn.io/mcp/all/ | Verified | 200 | |
| http (plaintext) | http://api.tinyfn.io/mcp/all/ | HTTPS enforced | 301 | https://api.tinyfn.io/mcp/all/ |
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 →
validate_credit_card ~29
Validate a credit card number using Luhn algorithm.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | Credit card number |
| Name | Type | Req | Description |
|---|---|---|---|
| card_type | – | – | – |
| is_valid | boolean | yes | – |
| length | – | – | – |
| number | string | yes | – |
| reason | – | – | – |
No examples provided.
validate_date ~35
Validate a date string.
| Name | Type | Req | Description |
|---|---|---|---|
| date_str | string | yes | Date string to validate |
| format | string | – | Expected date format |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| error | – | – | – |
| format | string | yes | – |
| is_valid | boolean | yes | – |
| parsed | – | – | – |
No examples provided.
validate_domain ~24
Validate a domain name.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| is_valid | boolean | yes | – |
| subdomain | – | – | – |
| tld | – | – | – |
No examples provided.
validate_email ~24
Validate an email address.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| is_valid | boolean | yes | – |
| parts | object | yes | – |
No examples provided.
validate_hex ~25
Validate a hexadecimal string.
| Name | Type | Req | Description |
|---|---|---|---|
| hex_str | string | yes | Hex string to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| hex | string | yes | – |
| is_valid | boolean | yes | – |
| length | – | – | – |
No examples provided.
validate_ip ~30
Validate an IP address (v4 or v6).
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IP address to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | – |
| is_global | – | – | – |
| is_loopback | – | – | – |
| is_private | – | – | – |
| is_valid | boolean | yes | – |
| version | – | – | – |
No examples provided.
validate_ip_2 ~31
Validate if a string is a valid IP address.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IP address to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | – |
| is_ipv4 | boolean | yes | – |
| is_ipv6 | boolean | yes | – |
| valid | boolean | yes | – |
| version | – | – | – |
No examples provided.
validate_json ~24
Validate JSON syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| json_str | string | yes | JSON string to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | – |
| is_valid | boolean | yes | – |
| json | string | yes | – |
| type | – | – | – |
No examples provided.
validate_json_2 ~30
Validate if a string is valid JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| json_string | string | yes | JSON string to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | – |
| error_column | – | – | – |
| error_line | – | – | – |
| error_position | – | – | – |
| type | – | – | – |
| valid | boolean | yes | – |
No examples provided.
validate_mac ~24
Validate a MAC address.
| Name | Type | Req | Description |
|---|---|---|---|
| mac | string | yes | MAC address to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| is_valid | boolean | yes | – |
| mac | string | yes | – |
| normalized | – | – | – |
No examples provided.
validate_password_strength ~23
Check password strength.
| Name | Type | Req | Description |
|---|---|---|---|
| password | string | yes | Password to check |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | – | yes | – |
| max_score | integer | yes | – |
| password_length | integer | yes | – |
| score | integer | yes | – |
| strength | string | yes | – |
No examples provided.
validate_pattern ~31
Validate if a regex pattern is syntactically correct.
| Name | Type | Req | Description |
|---|---|---|---|
| pattern | string | yes | Regular expression pattern to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | – |
| pattern | string | yes | – |
| valid | boolean | yes | – |
No examples provided.
validate_phone ~35
Validate a phone number.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country code for validation |
| phone | string | yes | Phone number to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| cleaned | string | yes | – |
| country | string | yes | – |
| is_valid | boolean | yes | – |
| phone | string | yes | – |
No examples provided.
validate_semver ~26
Validate a semantic version string.
| Name | Type | Req | Description |
|---|---|---|---|
| version | string | yes | Semantic version to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| is_valid | boolean | yes | – |
| parts | object | yes | – |
| version | string | yes | – |
No examples provided.
validate_url ~22
Validate a URL.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| is_valid | boolean | yes | – |
| parts | object | yes | – |
| url | string | yes | – |
No examples provided.
validate_uuid ~23
Validate a UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid_str | string | yes | UUID to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| is_valid | boolean | yes | – |
| uuid | string | yes | – |
| version | – | – | – |
No examples provided.
verify_hash ~44
Verify a hash matches the text.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | Algorithm used |
| hash_value | string | yes | Hash to verify |
| text | string | yes | Original text |
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | – | – | – |
| computed_hash | – | – | – |
| error | – | – | – |
| matches | – | – | – |
No examples provided.
week_number ~29
Get the ISO week number of a date.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date (YYYY-MM-DD) |
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | – |
| date | – | – | – |
| day_name | – | – | – |
| day_of_week | – | – | – |
| error | – | – | – |
| iso_year | – | – | – |
| week_number | – | – | – |
No examples provided.
week_number_2 ~32
Get the ISO week number for a date.
| Name | Type | Req | Description |
|---|---|---|---|
| datetime_str | string | yes | Datetime in ISO format |
| Name | Type | Req | Description |
|---|---|---|---|
| datetime | – | – | – |
| day_name | – | – | – |
| day_of_week | – | – | – |
| error | – | – | – |
| iso_week | – | – | – |
| iso_year | – | – | – |
No examples provided.
word_count ~26
Count words in text.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to count words in |
| Name | Type | Req | Description |
|---|---|---|---|
| character_count | integer | yes | – |
| character_count_no_spaces | integer | yes | – |
| text | string | yes | – |
| word_count | integer | yes | – |
No examples provided.
would_you_rather ~19
Get a 'Would You Rather' question.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| option_a | string | yes | – |
| option_b | string | yes | – |
| question | string | yes | – |
No examples provided.
yes_no ~27
Get a random yes or no answer.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | Your yes/no question |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| question | string | yes | – |
No examples provided.
What is the TinyFn MCP server?
TinyFn is an MCP server listed in the public MCP registry as io.tinyfn/tinyfn. 500+ deterministic tools for AI agents: math, conversion, validation, hashing, encoding, date/time. This page covers its hosted endpoint (https://api.tinyfn.io/mcp/all/).
Is the TinyFn MCP server safe to use?
TinyFn scores 75 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 TinyFn MCP server expose?
TinyFn exposes 572 tools: is_even, is_odd, is_prime, is_positive, is_negative, and 567 more. Their descriptions and schemas cost roughly 20,637 tokens of context every time the server is loaded.
Does the TinyFn MCP server require authentication?
No. We connected to TinyFn without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TinyFn MCP server still maintained?
TinyFn is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.