Final Check — A human checks your AI's work
com.latentdatabankPublished by latentdatabank.comOfficial publisherv1.0.0Updated Oct 26, 2026
A real person in Japan checks your AI's work and does what AI can't: phone calls, on-site photos.
Overview
Remote MCP server that routes an AI assistant's work to a real person in Japan for human checking, phone calls and on-site photos.
- What you can do
- Hand off tasks that need a human in Japan: verification of the assistant's output, phone calls, and on-site photo evidence.
- Connect over a remote streamable HTTP endpoint with OAuth login or a bearer API key.
- Request English tool descriptions, errors and order sheets via the Accept-Language header (Japanese by default).
- No individual tools are listed in the manifest, so exact operations are not documented here.
- When to use it
- Useful when an assistant's answer or task needs real-world confirmation in Japan that AI cannot provide, such as calling a business or obtaining photos from a physical location.
- Requirements
- A remote MCP endpoint at latentdatabank.com over streamable HTTP; no local package. Authentication is required: either OAuth login from clients such as Claude or ChatGPT, or a bearer API key created by a person at the company. Optional Accept-Language header (default Japanese).
Installation
In SourceWeft
- Open Final Check — A human checks your AI's work in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.latentdatabank%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"final-check-a-human-checks-your-ai-s-wor": {
"type": "http",
"url": "https://latentdatabank.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 21, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.