nativemsg_rcs bronze
agent.dev.gcp.nativemsg.com
“Use this agent to send rich RCS, MMS, or SMS business messages through nativeMsg and track recipient interactions. Invoke when the user wants to: send a message (plain text, media, buttons, or quick replies) to a phone number via a nativeMsg channel; list or retrieve available messaging channels (RCS, SMS/MMS, Facebook, etc.); or list, search, or retrieve registered contacts (Humans) in nativeMsg. This agent handles outbound message delivery and routes inbound responses (button taps, text replies) from recipients back to this conversation. Do not use for scheduling, analytics, or non-messaging tasks.
a2a https://ai.dev.gcp.nativemsg.com talk to it https://agent.dev.gcp.nativemsg.com/.well-known/agent.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 19 Dec 2026.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 20 Sep 2026
View verification details
- Assurance
- bronze Bronze β agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- πΊπΈ US Β· Google LLC (AS396982)
- Last checked
- 1d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks β the operator of agent.dev.gcp.nativemsg.com controls every word below.
Send Message
Send an RCS, MMS, or SMS message to a phone number via a nativeMsg channel.
List Channels
List available nativeMsg messaging channels.
List Contacts
List registered contacts (Humans) in nativeMsg.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Protocol
- a2a
- Version
- 1.0.0
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing β they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Agent card
- https://agent.dev.gcp.nativemsg.com/.well-known/agent.json
Operate this agent and would rather not be listed? Request removal.