← LastDatabase MCP Server Overview

LastDatabase MCP Server Documentation

Connect MCP-compatible AI clients and agents to LastDatabase for authorized B2B contact search, verified contact unlocking, business email verification and subscription allowance access.

What is the LastDatabase MCP Server?

The LastDatabase MCP Server provides a structured interface between MCP-compatible AI applications and authorized LastDatabase customer accounts.

Instead of manually copying search criteria between an AI assistant and the LastDatabase dashboard, an authorized AI client can discover permitted tools and invoke them through Model Context Protocol.

Tool availability is determined by the OAuth scopes granted to the connected account. A client only sees MCP tools that its authorization permits.

Available MCP Tools

The current LastDatabase MCP implementation exposes four customer-facing tools when the corresponding OAuth scopes are available.

Authentication and authorization

The LastDatabase MCP resource requires authorization. Unauthenticated access to the protected MCP endpoint is rejected. OAuth metadata is published separately so compatible clients can discover the authorization requirements.

The canonical protected MCP resource is:

https://lastdatabase.com/mcp

Protected-resource metadata is available at:

https://lastdatabase.com/.well-known/oauth-protected-resource/mcp

Authorization is scope-aware. For example, an account with people:search can discover the people search functionality. Email verification requires email:verify, while allowance reading requires credits:read.

Search B2B contacts with search_people

The search_people tool searches LastDatabase B2B contact records. At least one search filter is required.

Supported search fields include:

Example AI request

Use LastDatabase to search for 5 B2B contacts
in the technology industry in the USA.
Do not unlock any contacts.

Masked search behavior

Search is non-charging. Protected email addresses remain masked unless the connected customer already owns the contact. The search result also identifies whether an email is already unlocked.

Unlock a contact with unlock_people

The unlock_people tool accepts a lead_id returned by a contact search.

{
  "lead_id": 26515544
}

Before a new subscription record is consumed, LastDatabase checks entitlement, applies suppression screening and performs JIT email verification.

JIT verification flow

1. The requested lead is resolved.
2. Existing customer ownership is checked.
3. Existing paid-order ownership is checked.
4. Subscription eligibility is checked when required.
5. Suppression rules are applied.
6. The email is evaluated by the JIT verification process.
7. The protected email is released only when the required verified-delivery criteria are satisfied.

A definitively verified, SMTP-accepted mailbox can proceed through the eligible unlock path.

Invalid, risky, catch-all, disposable, unreachable, unknown or temporarily inconclusive results are not unlocked through the new subscription-consumption path.

Previously owned contacts

A contact already owned by the customer is not charged again. A contact previously purchased through an eligible paid order can also be returned without consuming the subscription allowance again.

Example AI request

Use LastDatabase to unlock B2B record ID 26515544.
Show me the JIT verification result.
If the email is not valid for verified delivery,
do not consume a record and tell me to try the next contact.

Verify an email with verify_email

The verify_email tool accepts one business email address and sends it to the LastDatabase verification engine.

{
  "email": "test@example.com"
}

This tool requires the email:verify OAuth scope. Its purpose is email verification rather than unlocking a protected B2B search result.

Example AI request

Use LastDatabase to verify test@example.com

Check allowance with get_credits

The get_credits tool returns the connected LastDatabase customer's subscription record allowance. It requires the credits:read scope.

It accepts no tool arguments.

Example AI request

Use LastDatabase to tell me how many records I have remaining.
Do not search for or unlock any contacts.

When does MCP consume a record?

Example AI-agent workflow

A typical MCP-assisted prospecting workflow can keep search and consumption separate:

1. Ask LastDatabase for the remaining record allowance.

2. Search for matching B2B contacts.

3. Review IDs, names, companies, titles and masked emails.

4. Select a specific contact.

5. Request unlock for that lead ID.

6. LastDatabase performs entitlement, suppression and
   JIT verification checks.

7. If eligible, return the unlocked contact.

8. Check the remaining allowance again.

MCP protocol behavior

The LastDatabase MCP server supports MCP tool discovery and tool invocation through the protected resource.

Tool discovery is authorization-aware. The server builds the available tool list from the scopes granted to the authenticated connection.

The implementation uses MCP tool annotations to communicate behavior such as read-only status, destructive behavior and open-world interaction characteristics.

Common MCP errors

Security and responsible use

MCP access does not make LastDatabase data publicly accessible. The MCP resource is protected, authorization is account-bound, and tool availability depends on granted scopes.

Search results protect email addresses until the connected customer already owns the contact or an eligible unlock succeeds.

Customers remain responsible for using exported or unlocked data in accordance with applicable law, contractual requirements and LastDatabase policies.

See the Compliance, Privacy Center, Data Privacy & Responsible Use and Methodology pages for additional information.

MCP or REST API?

MCP is designed for compatible AI clients and agents that discover and invoke structured tools. The LastDatabase API is intended for conventional application-to-application integrations.

Developers building a traditional backend integration should also review the LastDatabase API documentation and API authentication guide.

Frequently asked questions