Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Automate America

REMOTE · AUTOMATEAMERICA.COM

Find skilled professionals and open work, and act for a member with their consent.

+3 this week 73 Trust /100

Last scanned (22 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 123356 tokens (~334/item across 369 items; 368 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management46
  • Stability check failed: schema churn in the 14 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 58 additions. See how to fix → Fail
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 48 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 370 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Nov 26 +1
    • Stability: 0.40 → fail ▼ security
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Nov 26 0
    • Schema quality: 297 → 333 ▼ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 15 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 14 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://automateamerica.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=automateamerica.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 1 Sept 2026 17 Mar 2027 RSA 2048 SHA256-RSA 997cbb0eaa6744ac3a3b20f031831c6
SANs: automateamerica.com, *.automateamerica.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of automateamerica.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
automateamerica.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self';style-src 'self' 'unsafe-inline' https:;script-src 'self' 'unsafe-inline' 'unsafe-eval' https:;img-src 'self' data: https: http:;connect-src 'self' https: http:;font-src 'self' https: data:;object-src 'none';media-src 'self' https:;frame-src 'self';base-uri 'self';form-action 'self';frame-ancestors 'none';script-src-attr 'none';upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://automateamerica.com/api/mcp Verified 200
http (plaintext) http://automateamerica.com/api/mcp HTTPS enforced 301 https://automateamerica.com:443/api/mcp
MCP tools · 368 exposed · ~122,625 tokens partial

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_my_post ~410

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
textstring––

No output schema declared.

No examples provided.

decide_applicant ~780

No description provided.

NameTypeReqDescription
applicationIdintegeryes–
askstring––
confirmationTokenstring––
endDatestring––
jobIdintegeryes–
keystringyes–
messagestring––
reasonstring––
sourcestring––
startDatestring––
typestring––

No output schema declared.

No examples provided.

decline_connection ~390

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
requestIdintegeryes–

No output schema declared.

No examples provided.

decline_connection_story ~373

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
idintegeryes–

No output schema declared.

No examples provided.

decline_crew_ask ~411

No description provided.

NameTypeReqDescription
askstring––
askIdintegeryes–
confirmationTokenstring––

No output schema declared.

No examples provided.

decline_endorse_ask ~466

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
obligationIdintegeryes–

No output schema declared.

No examples provided.

decline_interview_request ~427

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
reasonstring––
requestIdintegeryes–

No output schema declared.

No examples provided.

decline_my_rate_change ~461

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
idintegeryes–
jobIdintegeryes–
reasonstring|null––

No output schema declared.

No examples provided.

decline_offer ~470

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
offerIdintegeryes–
sourcestring––

No output schema declared.

No examples provided.

delete_my_comment ~467

No description provided.

NameTypeReqDescription
askstring––
commentIdintegeryes–
confirmationTokenstring––
idintegeryes–
typestringyes–

No output schema declared.

No examples provided.

delete_my_connection_story ~402

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
idintegeryes–

No output schema declared.

No examples provided.

delete_my_expense_report ~140

No description provided.

NameTypeReqDescription
idintegeryes–

No output schema declared.

No examples provided.

delete_my_message ~539

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
messageIdintegeryes–
userIdintegeryes–

No output schema declared.

No examples provided.

delete_my_post ~358

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
idintegeryes–

No output schema declared.

No examples provided.

delete_saved_search ~156

No description provided.

NameTypeReqDescription
idintegeryes–

No output schema declared.

No examples provided.

delete_timesheet_draft ~190

No description provided.

NameTypeReqDescription
idintegeryes–

No output schema declared.

No examples provided.

delete_work_draft ~151

No description provided.

NameTypeReqDescription
idintegeryes–

No output schema declared.

No examples provided.

draft_work_posting ~272

No description provided.

NameTypeReqDescription
postingobjectyes–

No output schema declared.

No examples provided.

edit_business_group ~458

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
descriptionstring|null––
idintegeryes–
namestring––
sectorstring|null––

No output schema declared.

No examples provided.

edit_my_comment ~574

No description provided.

NameTypeReqDescription
askstring––
commentIdintegeryes–
confirmationTokenstring––
idintegeryes–
textstring––
typestringyes–

No output schema declared.

No examples provided.

edit_saved_search ~194

No description provided.

NameTypeReqDescription
alertFrequencystring––
idintegeryes–
namestring––

No output schema declared.

No examples provided.

endorse_connection ~673

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
itemIdinteger––
ratinginteger––
relationshipTypestring––
sectionTypestring––
textstring––
withinteger––

No output schema declared.

No examples provided.

endorse_listing ~511

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
idintegeryes–
kindstringyes–

No output schema declared.

No examples provided.

extend_work_contract ~595

No description provided.

NameTypeReqDescription
askstring––
confirmationTokenstring––
idintegeryes–
newEndDatestring––
reasonstring––
typestringyes–
weeksinteger––

No output schema declared.

No examples provided.

find_work_for_me ~1,031

No description provided.

NameTypeReqDescription
applicationstring––
availableFromstring––
availableTostring––
citystring––
countrystring––
manufacturerstring––
maxRatenumber––
minRatenumber––
modelstring––
nearstring––
occupationstring––
occupationIdstring––
qstring––
radiusinteger––
skilledTradestring––
statestring––
typestring––

No output schema declared.

No examples provided.

get_ad_prices ~233

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_blog_post ~127

No description provided.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

get_boost_explain ~243

No description provided.

NameTypeReqDescription
kindstring––

No output schema declared.

No examples provided.

get_boost_prices ~186

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_business_group ~190

No description provided.

NameTypeReqDescription
keystringyes–

No output schema declared.

No examples provided.

get_company ~129

No description provided.

NameTypeReqDescription
idintegeryes–

No output schema declared.

No examples provided.

get_crew_expense_report ~160

No description provided.

NameTypeReqDescription
employeeIdintegeryes–
idintegeryes–

No output schema declared.

No examples provided.

get_crew_timesheet ~159

No description provided.

NameTypeReqDescription
employeeIdintegeryes–
idintegeryes–

No output schema declared.

No examples provided.

get_expense_report_to_approve ~162

No description provided.

NameTypeReqDescription
idintegeryes–

No output schema declared.

No examples provided.

get_like_state ~178

No description provided.

NameTypeReqDescription
idintegeryes–
typestringyes–

No output schema declared.

No examples provided.

get_my_account_type ~135

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_application ~212

No description provided.

NameTypeReqDescription
idintegeryes–
typestring––

No output schema declared.

No examples provided.

get_my_availability ~127

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_bill ~121

No description provided.

NameTypeReqDescription
idintegeryes–

No output schema declared.

No examples provided.

get_my_bill_payment_options ~218

No description provided.

NameTypeReqDescription
idintegeryes–

No output schema declared.

No examples provided.

get_my_boost_placements ~164

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_business_address ~139

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_business_contacts ~243

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_clearance ~119

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_company ~206

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_company_types ~121

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_connection_stories_visibility ~105

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_dashboard ~210

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_diverse_supplier ~106

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_my_draft ~138

No description provided.

NameTypeReqDescription
idintegeryes–

No output schema declared.

No examples provided.

Install

How do I install the Automate America MCP server?

Automate America is a hosted endpoint at https://automateamerica.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · automateamerica.com

# add to Claude Code
claude mcp add --transport http com-automateamerica-automate-america 'https://automateamerica.com/api/mcp'
Common questions

What is the Automate America MCP server?

Automate America is an MCP server listed in the public MCP registry as com.automateamerica/automate-america. Find skilled professionals and open work, and act for a member with their consent. This page covers its hosted endpoint (https://automateamerica.com/api/mcp).

Is the Automate America MCP server safe to use?

Automate America scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Does the Automate America MCP server require authentication?

No. We connected to Automate America without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Automate America MCP server still maintained?

Automate America is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Automate America MCP server?

VerifyMCP ran 13 checks on Automate America, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.