Nekuda WebMCP Discovery Bot
Run by Nekuda
How to detect Nekuda WebMCP Discovery Bot
Nekuda WebMCP Discovery Bot signs its requests, so you detect it by verifying the cryptographic signature on each request. A valid signature proves the request came from Nekuda; a copied user agent without the signature does not.
- Detection method
- SignedThe agent signs its requests, so its identity is verified cryptographically.
- Signals that identify it
- CryptographicA signed request verified cryptographically
- BehavioralHow the session clicks, types, moves and navigates, checked after the signature is verified
Every signal Verisoul checks for Nekuda WebMCP Discovery Bot
Nekuda WebMCP Discovery Bot signs its requests, so we verify who it is cryptographically, then check the rest of the session.
- Used
Cryptographic
A signed request verified cryptographically
- Not used
Network
Not needed to identify it
- Not used
Device
Not needed to identify it
- Used
Behavioral
How the session clicks, types, moves and navigates, checked after the signature is verified
How often you'll see it
Very uncommon
Rare, brand new, or not seen on Verisoul traffic yet
More from Nekuda
Questions about Nekuda WebMCP Discovery Bot
How do you detect Nekuda WebMCP Discovery Bot?
Nekuda WebMCP Discovery Bot signs its requests, so you detect it by verifying the cryptographic signature on each request. A valid signature proves the request came from Nekuda; a copied user agent without the signature does not.
What is Nekuda WebMCP Discovery Bot?
Nekuda WebMCP Discovery Bot is a crawler run by Nekuda that signs its requests.
Does Nekuda WebMCP Discovery Bot identify itself?
Yes. Nekuda WebMCP Discovery Bot signs its requests cryptographically, which is the strongest way an agent can identify itself.
Can a bot pretend to be Nekuda WebMCP Discovery Bot?
Not convincingly. A bot can copy Nekuda WebMCP Discovery Bot's user agent, but without Nekuda signing keys its requests fail verification and it is not labeled Nekuda WebMCP Discovery Bot.
How common is Nekuda WebMCP Discovery Bot?
Very uncommon. Rare, brand new, or not seen on Verisoul traffic yet.
What does the Verisoul API return for Nekuda WebMCP Discovery Bot?
Every session Verisoul identifies as Nekuda WebMCP Discovery Bot carries an agent block with id "nekuda_webmcp_discovery_bot", name, provider, type "crawler", detection_method "signed" and the detection_signals used (cryptographic, behavioral). Build rules on the id, type and detection method.