NF-e Access Key Validator MCP. Stop processing bad fiscal data keys.
NF-e Access Key Validator checks Brazilian Electronic Invoice (NF-e) access keys for structural integrity and compliance. This MCP validates complex 44-digit tax keys, ensuring they pass mathematical checksums (Modulo 11) and adhere to current tax authority standards before your system uses them.
Give Claude and any AI agent real-world access
Determines if a key's length and mathematical checksum are correct using the Modulo 11 algorithm.
Splits a valid access key into its core components, such as CNPJ and State Code.
Verifies that the extracted data fields follow current Brazilian tax authority regulations.
Ask an AI about this
Waiting for input…
What AI agents can do with NF-e Access Key Validator MCP (3 Tools)
These three tools allow you to validate NF-e access keys by checking their mathematical structure, pulling out individual business data points, and auditing compliance with official tax authority standards.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using NF-e Access Key Validator MCPExtract Key Metadata
Splits a working access key into its individual business parts like the CNPJ or State Code for inspection.
Validate Business Compliance
Checks if all components found in the key match current, allowed tax authority...
Verify Key Structure
Determines if an access key is valid by checking its length and running a...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with NF-e Access Key Validator, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Constant Tax Headache
Every time a batch of invoices comes in from a partner, your team has to manually check the key format. You're copying and pasting these 44-digit strings into internal tools or spreadsheets, running validation checks that only catch half the problems—maybe the length is right, but the underlying CNPJ number might be outdated or non-compliant.
With this MCP, you pass the entire batch to your agent. The system runs a complete audit: first checking the mathematical integrity of the key, then decomposing it into usable parts like the State Code and CNPJ. You get back a clean list, separating what's ready for processing from what needs human tax review—all without leaving your workflow.
Access Key Validator MCP: Guaranteed Compliance
You eliminate the need to run multiple validation scripts. Instead of having one tool check the math, another check the CNPJ format, and a third checking compliance against current tax rules, this MCP handles all three in sequence.
The result is confidence. You don't just know if the key *looks* right; you know it passes every regulatory hurdle required by Brazilian law. It changes your process from reactive troubleshooting to proactive data ingestion.
What NF-e Access Key Validator MCP does for your AI
Dealing with Brazilian fiscal data means handling complicated keys that can't just be treated like normal strings of numbers. This MCP lets you validate those NF-e access keys, confirming they are both mathematically correct and legally compliant right out of the gate. You input a key, and it doesn't just tell you 'yes' or 'no.' It breaks down exactly what that key means—extracting crucial data points like the CNPJ number, state code, and document model.
Furthermore, it checks those components against official tax authority rules. If your system needs reliable fiscal data for invoicing, this is essential. You can connect to this MCP through Vinkius, accessing these specialized tools alongside thousands of others in one place.
019ee7e4-2277-7213-9c5e-ff024edc5c50 How to set up NF-e Access Key Validator MCP
The bottom line is you get a definitive pass/fail grade on both structural integrity and regulatory compliance for any given NF-e key.
Pass the NF-e access key you need to check into this MCP.
The tool first runs a structural validation, confirming the length and checksum using Modulo 11. If that passes, it proceeds to decompose the key's components (CNPJ, State Code).
Finally, it audits those extracted components against current tax authority rules, giving you a full compliance report.
Who uses NF-e Access Key Validator MCP
Integration engineers, financial operations staff, and back-office tax specialists. You're the person whose job breaks when a single keystroke or bad data point causes an entire batch of invoices to fail processing.
Uses this MCP daily to validate incoming NF-e keys from partners, preventing manual rejections and ensuring high throughput during month-end closing.
Builds automated data pipelines that rely on external key validation before transmitting sensitive fiscal data to a core ERP system.
Runs compliance checks against newly received invoice keys to pre-audit their legality and structure against current Brazilian tax law.
Benefits of connecting NF-e Access Key Validator MCP
Prevents system failures by verifying structure. Using verify_key_structure immediately tells you if a key fails the Modulo 11 checksum or length check, saving runtime errors down the line.
Extracts necessary metadata instantly. Instead of manual parsing, the extract_key_metadata tool pulls out the CNPJ and State Code so your agent can use them directly in subsequent actions.
Guarantees regulatory compliance. The validate_business_compliance tool audits components against official tax standards, meaning you process keys that are legally sound from day one.
Reduces manual verification steps. You no longer need multiple systems or spreadsheets to check if a key is valid; this MCP handles the full lifecycle validation in one place.
Increases data reliability for finance teams. By ensuring every incoming NF-e key passes both structural and compliance checks, your team gets cleaner data for reporting.
NF-e Access Key Validator MCP use cases
Processing a Batch of Partner Invoices
A financial operations specialist receives 500 invoices from a partner. Instead of running each key manually through multiple validation scripts, they ask their agent to run the batch against this MCP. The tool first uses verify_key_structure on every single key. It then groups all keys that pass into two buckets: 'Compliant' and 'Needs Review,' dramatically speeding up reconciliation.
Integrating a New Partner Feed
An integration engineer must connect the core ERP to a new supplier feed containing NF-e keys. To prevent data corruption, they use extract_key_metadata first. This allows them to pull out only the necessary CNPJ and State Code fields, confirming the key format before writing any data into the live system.
Auditing Historical Data for Tax Changes
A tax compliance analyst needs to know if a set of old keys still meet current tax authority standards. They run the batch through validate_business_compliance. This checks the components against today's rules, flagging any historical keys that might now be considered non-compliant.
Real-time Data Gateway Check
A payments gateway needs to quickly verify a key as soon as it arrives. They use this MCP for instant validation. If the verify_key_structure check fails, the payment is instantly rejected with a clear structural error code, preventing bad transactions.
NF-e Access Key Validator MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Treating Keys as Simple Strings
Trying to use basic regex or simple database lookups to confirm if an NF-e key is valid. This fails because it ignores the complex mathematical checksum (Modulo 11) and compliance rules.
You must first run verify_key_structure to check the math, then pass the result through validate_business_compliance to ensure the components meet tax standards.
Over-relying on Key Format Alone
Assuming that because a key has 44 digits, it is usable. This ignores potential issues like an outdated CNPJ structure or non-compliant State Codes.
Always use extract_key_metadata to get the individual components, and then pass those parts into validate_business_compliance for proper auditing.
Skipping Initial Structural Checks
Feeding a key directly into a processing system without first checking its format. The process will halt at the checksum failure point, wasting time and resources.
Start with verify_key_structure. If it fails, you stop immediately before attempting to parse or validate anything else.
When to use NF-e Access Key Validator MCP
Use this MCP if your work involves processing Brazilian fiscal data (NF-e) and reliability is critical. You need more than just a basic format check; you require proof that the key's underlying components are mathematically sound and legally compliant according to tax authority standards. If your pain point is knowing whether an incoming batch of keys can be trusted for immediate processing, this is what you need.
Don't use this if all you need is basic text manipulation or simple data extraction from non-tax documents. For generic parsing tasks, a standard string utility tool works fine. But because NF-e keys are highly regulated and complex, treating them as anything less than multi-layered validation (structure + metadata + compliance) will cause failures.
Frequently asked questions about NF-e Access Key Validator MCP
How does NF-e Access Key Validator check for structural validity? +
The MCP uses the verify_key_structure tool. This function checks both the required 44-digit length and runs a mathematical checksum using the Modulo 11 algorithm to ensure the key is mathematically sound.
What information can I get from extract_key_metadata? +
The extract_key_metadata tool breaks down the key into its core components. You'll receive distinct fields, including the CNPJ (company tax ID), State Code, Model number, and Series.
Does this MCP only check if the key is formatted correctly? +
No. It goes much further than format. While verify_key_structure checks the math, you also must use validate_business_compliance to ensure those components comply with actual tax authority rules.
Can NF-e Access Key Validator handle different types of invoices? +
It focuses specifically on Brazilian Electronic Invoice (NF-e) keys. The tools are designed around the required structure and compliance framework for that specific document type in Brazil.
Is this MCP faster than using a dedicated tax software tool? +
When integrated into an automated agent workflow, it is much faster. It lets you run validation checks against thousands of keys instantly without needing to switch between separate vendor platforms or manual interfaces.