Terms of Service — Data.gov MCP Server (by BLEN)

Last updated: 2026-10-08

1. Acceptance and scope

By accessing or using the BLEN-hosted Data.gov MCP Server (the Service, operated by BLEN, Inc.), you agree to these terms. If you do not agree, do not use the Service. If you use it on behalf of an organization, you represent that you are authorized to accept these terms for that organization.

The underlying software is separately licensed under Apache-2.0. These hosted-service terms do not replace that license or restrict rights it grants. Self-hosted deployments are operated under their operators' terms and policies.

2. Independent service and data sources

The Service is an independent, read-only client for a supported subset of NPS, OpenFEC, and GovInfo APIs participating in api.data.gov. It does not provide every api.data.gov service or the Data.gov dataset catalog. Source availability depends on agency service availability and the organization's key permissions and quotas.

BLEN is not affiliated with, sponsored by, or endorsed by the U.S. government, NPS, the Federal Election Commission, the Government Publishing Office, or api.data.gov. Third-party content remains subject to applicable rights and source notices. These terms grant no rights to government seals, trademarks, or third-party material beyond those otherwise available to you.

3. Accounts and organization credentials

Access requires Google sign-in or an operator-provisioned review login, authorized organization membership, and a registered MCP client. You are responsible for protecting your credentials and using only organizations and API keys you are authorized to access. Organization administrators are responsible for supplying an appropriately authorized agency key and coordinating membership changes and offboarding with the operator.

Enter the agency key only through the authenticated organization portal. Do not share Google secrets, agency keys, or MCP tokens in chats, tool arguments, scripts, or public issues. The agency's key terms and quotas continue to apply. Notify BLEN of suspected unauthorized use.

4. Informational use and accuracy

The Service is for informational and research purposes. It does not provide legal advice, determine compliance, make filings, issue permits, or replace authoritative government publications or professional judgment.

Upstream data may contain errors, omissions, or delays. Submitted code and AI clients may filter, calculate, or summarize results incorrectly. Verify source documents, dates, citations, and relevant agency guidance before relying on an answer. Public access to a record does not authorize every possible downstream use of its contents.

5. Acceptable use

You agree not to:

• Bypass or attempt to bypass authentication, organization boundaries, sandbox isolation, quotas, or other access controls.
• Submit code or queries intended to extract secrets, access host internals, target unsupported systems, modify upstream records, or cause excessive load.
• Send credentials, confidential records, or sensitive personal information through the tools.
• Use the Service unlawfully, infringe others' rights, or harass or target individuals using public records.
• Misrepresent Service outputs as government approval or an official determination.

We may limit, suspend, or block access to address violations, abuse, security incidents, or threats to service availability.

6. Limits and source availability

The Service applies request, execution, memory, and agency limits. Current execution limits include 15 seconds, 10 agency calls, and four in-flight agency calls per script. Organization members share an agency-request budget. Shared infrastructure and upstream quotas can affect multiple users. Limits may change, and upstream providers may become unavailable.

The tools are search_api, describe_schema, and execute. Execution accepts plain JavaScript using the registered read-only SDK surface. The Service does not submit public comments, make filings, or perform other actions that modify government records. Compatibility with every MCP client is not guaranteed; actual Gemini Enterprise interoperability has not yet been verified.

7. Privacy

The Privacy Policy describes identity and organization information, encrypted keys, OAuth records, tool requests, upstream disclosures, logs, and retention. Your MCP client, identity provider, upstream agencies, and any self-hosted operator have separate practices and terms.

8. Availability and warranty

The Service is provided "as is" and "as available". To the maximum extent permitted by law, BLEN disclaims warranties, including merchantability, fitness for a particular purpose, and non-infringement. We do not guarantee accuracy, uninterrupted availability, compatibility with every MCP client, or continued free access. We may change or discontinue the hosted Service.

9. Liability

To the maximum extent permitted by law, BLEN, Inc. disclaims liability for direct, indirect, incidental, special, or consequential damages arising from use of or inability to use the Service. Nothing in these terms excludes liability that cannot lawfully be excluded.

10. Changes

We may update these terms. Material changes will be noted in the repository changelog at least 14 days before taking effect for the hosted Service. If you do not agree to revised terms, stop using the Service.

11. Governing law

These terms are governed by the laws of Delaware, USA, subject to applicable mandatory law.

12. Contact

Questions, privacy requests, support, and private vulnerability reports: opensource@blencorp.com. General support is also available through BLEN's contact page.