
Verifreta Carrier Lookup
io.github.humayuntanwarPublished by GitHub account humayuntanwarv1.1.0Updated Oct 1, 2026
Carrier first-look for freight brokers: DOT, MC/MX/FF, and name. SAFER/L&I stay source of truth.
The publisher's own server: Verifreta Carrier Lookup
Overview
Lets an assistant look up US freight carrier details by DOT number, MC/MX/FF number, or carrier name.
- What you can do
- Provides a carrier first-look lookup for freight brokers, accepting DOT numbers, MC/MX/FF numbers, or carrier names as search inputs. It returns carrier information to help identify and verify a carrier before deeper checks. The registry notes that SAFER and L&I remain the source of truth, so results are a starting point rather than an authoritative record.
- When to use it
- Useful when a broker or logistics assistant needs a quick first pass on a carrier from a DOT, MC/MX/FF number, or name before confirming details in official systems. Best treated as a preliminary lookup, not a compliance decision.
- Requirements
- Remote MCP endpoint at over streamable HTTP. No packages, environment variables, headers, or authentication are declared, so it appears to need only network access.
Installation
In SourceWeft
- Open Verifreta Carrier Lookup in the dashboard and add it to a workspace.
- 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/io.github.humayuntanwar%2Fverifreta-carrier-lookup/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.
{
"mcpServers": {
"verifreta-carrier-lookup": {
"type": "http",
"url": "https://www.verifreta.com/api/mcp"
}
}
}Tools
0Version history
1- v1.1.0LatestSep 26, 2026
Score
25% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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.
- License10 pts
Declare a license in the repository or the registry entry.