LLPROBeta

Home / Businesses / File Extension and MIME Type Match

File Extension and MIME Type Match

Check that each file's extension agrees with the MIME type sent, against the IANA media type registry: mismatches, obsolete or unregistered types, double extensions, signed; names are not echoed.

Testing

What it does
Check that each file's extension agrees with the MIME type sent, against the IANA media type registry: mismatches, obsolete or unregistered types, double extensions, signed; names are not echoed.
Who it is for
Businesses.
Start in one step
Ask your agent to call file_extension_mime at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

File Extension and MIME Type Match is for agents that move, upload or accept files for a business (shared drives, upload forms, email attachments) and need to catch files whose name and declared type disagree before storing or opening them. Check whether each file's extension agrees with the MIME (media) type sent with it, before a file is stored, shared or opened. Send up to 100 file names with their MIME types; get back per file: match, mismatch, obsolete or unregistered type (with the registered one to use), generic type, unknown extension or no extension, the types registered for the extension and the extensions for the type, and a warning for double extensions like report.pdf.exe. File names are not echoed, only extensions. It is one of the Files and records department tools LLPRO builds for the work agents do across business software (Google Drive, Dropbox, OneDrive, Box). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that move, upload or accept files for a business (shared drives, upload forms, email attachments) and need to catch files whose name and declared type disagree before storing or opening them.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call, files up to 100 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not open or sniff the file's bytes, so it cannot tell whether the content really is that type (a renamed file passes if name and type agree). Does not cover every registered type: about 70 common ones; others show unknown_extension or mismatch with the reason. Does not echo file names. Not a malware or safety check.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "file_extension_mime", "arguments": {"files": [{"file_name": "invoice-0042.pdf", "mime_type": "application/pdf"}, {"file_name": "PHOTO.JPG", "mime_type": "image/jpeg"}, {"file_name": "export.csv", "mime_type": "text/csv; charset=utf-8"}]}}}

For agents

Tool file_extension_mime on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:f23jm5k6gqzsgiexdqvivxi2oe): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): a22ogJsnhZjWUggckWaGpE9bxHvKC1Zeb85EAMazSWc=

For agents that search MCP registries for MIME type, file extension, content type tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card